MIME-Version: 1.0
References: <01020195b987abd3-a008b77d-8c63-4931-80a4-be36a351c8b2-000000@eu-west-1.amazonses.com>
 <CAN_p2Qi_zie4aZqMcYuT-Y5CxyvUJ+nBAomQNJSPbBjrCPEXJw@mail.gmail.com>
 <01020195dd9e8337-c912f36d-54ef-4d3c-a00d-5e697b308d33-000000@eu-west-1.amazonses.com>
 <CAN_p2QghEHKeyTvb6Gc8F3y6wNm+dJXaCdrAnrV7TEq15Oh-pg@mail.gmail.com>
 <CAApHDvp3EDrVhGjmb21bceJ5-Y7iXKOn2UGG3-ngp_9ob_mpLw@mail.gmail.com> <CAN_p2QjXkBzyx55QAEGLfvWF0_UdusvxNmTykq_6jQsaaqjwTw@mail.gmail.com>
In-Reply-To: <CAN_p2QjXkBzyx55QAEGLfvWF0_UdusvxNmTykq_6jQsaaqjwTw@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Mon, 31 Mar 2025 10:16:01 -0700
Message-ID: <CAKFQuwbpQY9SV0vdWq7fyLk6pEOsDV3hprW7u1-_gQVGwU557g@mail.gmail.com>
Subject: Re: Querying one partition in a function takes locks on all partitions
To: Renan Alves Fonseca <renanfonseca@gmail.com>
Cc: David Rowley <dgrowleyml@gmail.com>, Evgeny Morozov <postgresql4@realityexists.net>, 
	pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000005af41b0631a6954e"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwbpQY9SV0vdWq7fyLk6pEOsDV3hprW7u1-_gQVGwU557g%40mail.gmail.com>
Precedence: bulk

--0000000000005af41b0631a6954e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 31, 2025 at 9:42=E2=80=AFAM Renan Alves Fonseca <renanfonseca@g=
mail.com>
wrote:

> I'm not sure if we should mention the fix or if we should mention a
> workaround...
>

Workarounds are ok but my observation is that "this may change in the
future" comments are pointless and should be stricken from the manual
because people are bad at predicting the future.  Just document what is and
don't string people along.  We never go back to old releases and say "This
was fixed in v17."

David J.

--0000000000005af41b0631a6954e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Mon, Mar 31, 2025 at 9:42=E2=80=AFAM Renan Alves Fonsec=
a &lt;<a href=3D"mailto:renanfonseca@gmail.com">renanfonseca@gmail.com</a>&=
gt; wrote:</span></div></div><div class=3D"gmail_quote gmail_quote_containe=
r"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">I&#39;m not sure if we=
 should mention the fix or if we should mention a<br>
workaround...<br></blockquote><div><br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif">Workarounds are ok but my o=
bservation is that &quot;this may change in the future&quot; comments are p=
ointless and should be stricken=C2=A0from the manual because people are bad=
 at predicting the future.=C2=A0 Just document what is and don&#39;t string=
 people along.=C2=A0 We never go back to old releases and say &quot;This wa=
s fixed in v17.&quot;</div><div class=3D"gmail_default" style=3D"font-famil=
y:arial,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif">David J.</div><div class=3D"gma=
il_default" style=3D"font-family:arial,helvetica,sans-serif"><br></div></di=
v></div>

--0000000000005af41b0631a6954e--