From: Tom Lane <tgl@sss.pgh.pa.us>
To: boekewurm+postgres@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16249: Partition pruning blocks on exclusively locked table partition
Date: Fri, 07 Feb 2020 14:17:44 -0500
Message-ID: <29415.1581103064@sss.pgh.pa.us> (raw)
In-Reply-To: <16249-0008721939743475@postgresql.org>
References: <16249-0008721939743475@postgresql.org>
PG Bug reporting form <noreply@postgresql.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, boekewurm+postgres@gmail.com
Subject: Re: BUG #16249: Partition pruning blocks on exclusively locked table partition
In-Reply-To: <29415.1581103064@sss.pgh.pa.us>
References: <16249-0008721939743475@postgresql.org> <29415.1581103064@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox