public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Tom Lane <[email protected]>
To: Alexander Lakhin <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: TupleDescAttr bounds checks
Date: Sat, 4 Apr 2026 23:52:02 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CA+TgmoacixUZVvi00hOjk_d9B4iYKswWP1gNqQ8Vfray-AcOCA@mail.gmail.com>
	<[email protected]>
	<CA+TgmoaiPqnV2ePY-DyQUVGnK5sJ5ryPCDYpn_+1Ua4JwfoqRw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CA+TgmoZgc1m5Z7RFf9U7s_DgXE8GqnOB95fEWurdKFMR_U2xpQ@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 04.04.26 17:38, Tom Lane wrote:
> I wrote:
>> But I bet this loop should throw an error for system columns, too,
>> since we surely won't have computed those either.
> 
> After poking at that: testing tableoid does sort of work, in that it
> reads as the OID of the target table named in COPY.  But I think any
> rational use for a test on tableoid here would be in connection with
> a partitioned target table, and the user would wish it to read as the
> OID of the destination partition.  So I think we should disallow
> tableoid along with the other system columns, pending somebody having
> the ambition to make that work.
> 
> So I propose the attached for HEAD.  (I couldn't resist the temptation
> to clean up adjacent comments.)  In the back branches it might be
> better to just ignore system columns here, on the tiny chance that
> somebody thinks they do something useful.

I think this is the same issue that was discussed here:

https://www.postgresql.org/message-id/flat/30c39ee8-bb11-4b8f-9697-45f7e018a8d3%40eisentraut.org

There was no conclusion there, but I agree with the proposal to prohibit 
this use.

view thread (10+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: TupleDescAttr bounds checks
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox