MIME-Version: 1.0
References: <LV3PR16MB6001AF4D05893E9FF4B3C746E6CE2@LV3PR16MB6001.namprd16.prod.outlook.com>
 <3528232.1718682678@sss.pgh.pa.us> <LV3PR16MB6001CD31C5982777BA9BA25EE6CE2@LV3PR16MB6001.namprd16.prod.outlook.com>
 <LV3PR16MB6001216CE02B2D908F9D87ECE6C82@LV3PR16MB6001.namprd16.prod.outlook.com>
 <LV3PR16MB60014D610A726368182ACC7EE6C92@LV3PR16MB6001.namprd16.prod.outlook.com>
 <597261.1718985078@sss.pgh.pa.us>
In-Reply-To: <597261.1718985078@sss.pgh.pa.us>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Fri, 21 Jun 2024 08:57:49 -0700
Message-ID: <CAKFQuwZ+_Hmn2oq=DmKyi=h2RJdONLtqH_j_eUdH_oYML3idhA@mail.gmail.com>
Subject: Re: RowDescription for a function does not include table OID
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Maxwell Dreytser <Maxwell.Dreytser@assistek.com>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000837dcc061b6880cb"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwZ%2B_Hmn2oq%3DDmKyi%3Dh2RJdONLtqH_j_eUdH_oYML3idhA%40mail.gmail.com>
Precedence: bulk

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

On Fri, Jun 21, 2024 at 8:51=E2=80=AFAM Tom Lane <tgl@sss.pgh.pa.us> wrote:

>
> The PG wire protocol specification [1] defines these fields thus:
>
>         If the field can be identified as a column of a specific
>         table, the object ID of the table; otherwise zero.
>
>         If the field can be identified as a column of a specific
>         table, the attribute number of the column; otherwise zero.
>
> My reading of that is that we should populate these fields only for
> the case of direct selection from a table.
>

s/can be identified as/is/g  ?

Experience shows people are inferring a lot from "can be identified" so we
should remove it.  "is" maybe over-simplifies a bit but in the correct
direction.

David J.

--000000000000837dcc061b6880cb
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 Fri, Jun 21, 2024 at 8:51=E2=80=AFAM Tom Lane &lt;<a hr=
ef=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt; wrote:</span><br>=
</div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><br>
The PG wire protocol specification [1] defines these fields thus:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 If the field can be identified as a column of a=
 specific<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 table, the object ID of the table; otherwise ze=
ro.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 If the field can be identified as a column of a=
 specific<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 table, the attribute number of the column; othe=
rwise zero.<br>
<br>
My reading of that is that we should populate these fields only for<br>
the case of direct selection from a table.<br></blockquote><div><br></div><=
div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif=
">s/can be identified as/is/g=C2=A0 ?</div><div class=3D"gmail_default" sty=
le=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=3D"gmail=
_default" style=3D"font-family:arial,helvetica,sans-serif">Experience shows=
 people are inferring a lot from &quot;can be identified&quot; so we should=
 remove it.=C2=A0 &quot;is&quot; maybe over-simplifies a bit but in the cor=
rect direction.</div><div class=3D"gmail_default" style=3D"font-family:aria=
l,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif">David J.</div></div></div>

--000000000000837dcc061b6880cb--