Re: Querying one partition in a function takes locks on all partitions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Renan Alves Fonseca <renanfonseca(at)gmail(dot)com>, Evgeny Morozov <postgresql4(at)realityexists(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Querying one partition in a function takes locks on all partitions
Date: 2025-03-31 03:21:53
Message-ID: 3753580.1743391313@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> On Sat, 29 Mar 2025 at 10:30, Renan Alves Fonseca
> <renanfonseca(at)gmail(dot)com> wrote:
>> Currently, in the SQL function path the plan is always generic. The
>> planner ignores the function arguments. The plan_cache_mode setting
>> has no effect in this path.
>> I agree that the docs should be more explicit about this. There is a
>> high penalty for using generic plans in complex functions.

> If you have any suggestions about where you think those should be
> added or wording for that, please feel free to suggest.

The issue's likely to be moot very shortly [1]. Maybe somebody
will be excited enough to consider changing the docs in the back
branches. But since it was like this for a couple of decades,
I bet not.

regards, tom lane

[1] https://www.postgresql.org/message-id/flat/8216639.NyiUUSuA9g%40aivenlaptop

In response to

Browse pgsql-general by date

  From Date Subject
Next Message 이현진 2025-03-31 04:44:10 SQL Server's WITH (NOLOCK) equivalent in PostgreSQL?
Previous Message David Rowley 2025-03-31 03:10:21 Re: Querying one partition in a function takes locks on all partitions