From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
cc: Maxwell Dreytser <Maxwell.Dreytser@assistek.com>,
        "pgsql-general@lists.postgresql.org"
 <pgsql-general@lists.postgresql.org>
Subject: Re: RowDescription for a function does not include table OID
In-reply-to: 
 <CAKFQuwZ+_Hmn2oq=DmKyi=h2RJdONLtqH_j_eUdH_oYML3idhA@mail.gmail.com>
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>
 <CAKFQuwZ+_Hmn2oq=DmKyi=h2RJdONLtqH_j_eUdH_oYML3idhA@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
	message dated "Fri, 21 Jun 2024 08:57:49 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <600216.1718986666.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Fri, 21 Jun 2024 12:17:46 -0400
Message-ID: <600217.1718986666@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/600217.1718986666%40sss.pgh.pa.us>
Precedence: bulk

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Fri, Jun 21, 2024 at 8:51 AM 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.

> 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.

I dunno, that seems to me to be just as open to argument if not
more so.  Perhaps some phrasing like "can be directly identified"?

The real point IMV is that it's based purely on parse analysis,
without looking into the behavior of views or functions (which
could change between parsing and execution, anyway).

			regards, tom lane