Re: Proposal to adjust typmod argument on base UDT input functions - Mailing list pgsql-hackers

From Octavio Alvarez
Subject Re: Proposal to adjust typmod argument on base UDT input functions
Date
Msg-id 942b104a-b678-48b2-a4b6-753f085d9cec@alvarezp.org
Whole thread Raw
In response to Re: Proposal to adjust typmod argument on base UDT input functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposal to adjust typmod argument on base UDT input functions
List pgsql-hackers
On 8/7/25 22:46, Tom Lane wrote:
> Octavio Alvarez <octalpg@alvarezp.org> writes:
>> I crafted the following rough patch which passes the target column
>> typmod on input functions instead of -1 for OIDs >= 16384. The intention
>> is to affect UDTs (user-defined types) only, not core data types.
> 
> I don't really see how we could accept this?  Wouldn't it break
> every existing extension datatype that uses typmod?

That was my first thought as well, but COPY sends the typmod directly 
already, so if they support COPY, they should already be compatible.

If an extension doesn't support COPY it means then it doesn't support 
the default pg_dump settings either.

Octavio.



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: event trigger support for PL/Python
Next
From: Tom Lane
Date:
Subject: Re: Proposal to adjust typmod argument on base UDT input functions