From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Regression in COPY FROM caused by 9f8377f7a2 |
Date: | 2023-09-25 21:49:42 |
Message-ID: | 281733.1695678582@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2023-09-25 Mo 11:06, Andrew Dunstan wrote:
>> On 2023-09-25 Mo 04:59, Laurenz Albe wrote:
>>> CREATE TABLE boom (t character varying(5) DEFAULT 'a long string');
> Thinking about this a little more, wouldn't it be better if we checked
> at the time we set the default that the value is actually valid for the
> given column? This is only one manifestation of a problem you could run
> into given this table definition.
I dunno, it seems at least possible that someone would do this
deliberately as a means of preventing the column from being defaulted.
In any case, the current behavior has stood for a very long time and
no one has complained that an error should be thrown sooner.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-09-25 21:58:23 | Re: How to update unicode mapping table? |
Previous Message | Tom Lane | 2023-09-25 21:45:33 | Re: Fix a wrong comment in setrefs.c |