Re: BUG #17650: For the sixth time, the clipping function in the 120 partition table planning stage fails

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: dafoer_x(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17650: For the sixth time, the clipping function in the 120 partition table planning stage fails
Date: 2022-10-18 13:50:17
Message-ID: 20221018135017.cefttdymnmooh4af@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Tue, Oct 18, 2022 at 01:11:13PM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17650
> Logged by: dafoer
> Email address: dafoer_x(at)163(dot)com
> PostgreSQL version: 14.0

Unrelated but you should definitely update to the latest minor version,
currently 14.5

> Operating system: centos7.6
> Description:
>
> The clipping function of partition table cannot be carried out normally in
> the planning stage. The extension protocol cannot be clipped in the sixth
> execution. When concurrency is high, lock contention is serious

I'm not sure I fully understand. Are you saying that partition pruning (1)
doesn't happen after 6 execution of a prepared statement? If yes, it's not a
bug but a known behavior of generic plans. You can dynamically set
plan_cache_mode to force_custom_plan for the cases where generic plans are
known to behave poorly.

[1] https://www.postgresql.org/docs/current/ddl-partitioning.html#DDL-PARTITION-PRUNING

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-10-18 14:05:38 Re: BUG #17650: For the sixth time, the clipping function in the 120 partition table planning stage fails
Previous Message Julien Rouhaud 2022-10-18 13:29:15 Re: BUG #17649: With libpg5 15.0 psql 10.22 uses HOME variable instead of uid and /etc/passwd to select .pgpass file