Re: Add mention in docs about locking all partitions for generic plans

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tender Wang <tndrwang(at)gmail(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add mention in docs about locking all partitions for generic plans
Date: 2025-03-30 23:19:38
Message-ID: CAApHDvogvzANoTOCyXUWgEuPFx1nT6S63aAN0bDRSJ=TaGBWew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 24 Mar 2025 at 22:19, Tender Wang <tndrwang(at)gmail(dot)com> wrote:
>> Maybe I was wrong about writing nothing in master's docs. It might
>> still be important to detail this. I don't know the best way to phrase
>> that, but maybe something along the lines of: "The query planner
>> obtains locks for all partitions which are part of the plan. However,
>> when the executor uses a cached plan, locks are only obtained on the
>> partitions which remain after partition pruning done during the
>> initialization phase of execution, i.e., the ones shown in the EXPLAIN
>> output and not the ones referred to by the “Subplans Removed”
>> property.".
>>
>> Any opinions?
>
> The above sentence looks good to me.

Thanks for looking.

I've attached the master and the <= v17 in patch form. Also, the
compiled HTML for ease of review.

I'll push these in the next few days unless anyone else wants to voice
their opinions.

David

Attachment Content-Type Size
ddl-partitioning.html.zip application/x-zip-compressed 31.0 KB
v17-0001-Doc-add-information-about-partition-locking.patch application/octet-stream 1.4 KB
v18-0001-Doc-add-information-about-partition-locking.patch application/octet-stream 1.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-03-30 23:46:57 Re: AIO v2.5
Previous Message Andres Freund 2025-03-30 23:13:56 Re: AIO v2.5