Re: pgsql: Support partition pruning at execution time

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: 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:21:18
Message-ID: CAKJS1f_77en0Rv=r_zJWnYe8cD04BQ5QrrsKe5uJVL2uSxFCuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 8 April 2018 at 15:02, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> On 8 April 2018 at 14:56, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
>> It happens 12 or 13 times on my machine, then does not happen again
>> for 60 seconds, then happens again.
>
> Setting autovacuum_naptime to 10 seconds makes it occur in 10 second
> intervals...

Ok, I thought it might have been some concurrent vacuum on the table
but the only tables I see being vacuumed are system tables.

I tried performing a manual vacuum of each of these and could not get
it to trigger, but then I did:

select * from pg_class;

from another session and then the script starts spitting out some errors.

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2018-04-08 03:25:32 Re: pgsql: Support partition pruning at execution time
Previous Message Andrew Gierth 2018-04-08 03:21:10 Re: pgsql: Support partition pruning at execution time

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2018-04-08 03:25:32 Re: pgsql: Support partition pruning at execution time
Previous Message Andrew Gierth 2018-04-08 03:21:10 Re: pgsql: Support partition pruning at execution time