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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: boekewurm+postgres(at)gmail(dot)com
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 19:17:44
Message-ID: 29415.1581103064@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2020-02-07 20:19:48 Re: FK violation in partitioned table after truncating a referenced partition
Previous Message Tom Lane 2020-02-07 19:12:53 Re: BUG #16248: ALTER SYSTEM quoting of values does not work as expected