| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Support partition pruning at execution time |
| Date: | 2018-04-08 03:25:32 |
| Message-ID: | CAKJS1f9hfaPBkG6vKJV3aFZC6u5rBUwxnXRA1fOueLxudmY4Ow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 8 April 2018 at 15:21, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
> David> Setting autovacuum_naptime to 10 seconds makes it occur in 10
> David> second intervals...
>
> Analyze (including auto-analyze on a different table entirely) has a
> snapshot, which can hold back OldestXmin, hence preventing the
> all-visible flag from being set.
urg, that's true.
Seems like there's no bugs here then;
begin work;
set transaction isolation level repeatable read;
select * from pg_class;
-- do nothing
makes the script go crazy.
You're right, thanks.
I guess the patch I sent is the way forward with this.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2018-04-08 03:34:22 | Re: pgsql: Support partition pruning at execution time |
| Previous Message | David Rowley | 2018-04-08 03:21:18 | Re: pgsql: Support partition pruning at execution time |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2018-04-08 03:27:45 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Previous Message | David Rowley | 2018-04-08 03:21:18 | Re: pgsql: Support partition pruning at execution time |