Re: BUG #16249: Partition pruning blocks on exclusively locked table partition

From: 0010203112132233 <boekewurm(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16249: Partition pruning blocks on exclusively locked table partition
Date: 2020-02-07 20:26:12
Message-ID: CAEze2Wi-jbSY4Q5OcdvN1GVbU6Za=d+HGRUfos1qa83R6_ZZKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 7 Feb 2020 at 20:17, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > In my humble opinion, this query should not be blocked during planning, as
> > the partition can be pruned directly from the plan with the partition
> > information that is available from the parent table: Partition information
> > can be updated when the partition is locked, but through the parent
> > partitioned table.
>
> This case has been improved in PG v12. It is operating as designed in
> v11, however.
>
> regards, tom lane

Ah, I indeed hadn't tested pg12 yet, but you are indeed correct. I
guess I'll then have to wait for pg12 to become generally available on
RDS.

Anyway, thanks for the help, and sorry for taking your time.

regards,

Matthias

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2020-02-07 21:30:51 Re: Another FK violation when referencing a multi-level partitioned table
Previous Message Alvaro Herrera 2020-02-07 20:23:15 Re: FK violation in partitioned table after truncating a referenced partition