Re: Proposal to adjust typmod argument on base UDT input functions

From: Octavio Alvarez <octalpg(at)alvarezp(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Proposal to adjust typmod argument on base UDT input functions
Date: 2025-08-08 05:05:47
Message-ID: 942b104a-b678-48b2-a4b6-753f085d9cec@alvarezp.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/7/25 22:46, Tom Lane wrote:
> Octavio Alvarez <octalpg(at)alvarezp(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-08-08 05:18:45 Re: Proposal to adjust typmod argument on base UDT input functions
Previous Message Pavel Stehule 2025-08-08 05:04:34 Re: event trigger support for PL/Python