Re: pgsql: Support partition pruning at execution time - Mailing list pgsql-committers

From David Rowley
Subject Re: pgsql: Support partition pruning at execution time
Date
Msg-id CAKJS1f_yjtHDJnDzx1uuR_3D7beDVAkNQfWJhRLA1gvPCzkAhg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Support partition pruning at execution time  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: pgsql: Support partition pruning at execution time  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-committers
On 8 April 2018 at 15:34, Andrew Gierth <andrew@tao11.riddles.org.uk> wrote:
> You can't ever assume that data you just inserted will become
> all-visible just because you just vacuumed the table, unless you know
> that there is NO concurrent activity that might have a snapshot (and no
> other possible reason why OldestXmin might be older than your insert).

Thanks. I got it. It just slipped my slightly paranoid and sleep deprived mind.

I've attached my proposed fix for the unstable regression tests. I
removed the vacuums I'd added in the last version and commented why
we're doing set enable_indesonlyscan = off;

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-committers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: pgsql: Support partition pruning at execution time
Next
From: Andrew Gierth
Date:
Subject: pgsql: Support index INCLUDE in the AM properties interface.