From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Sergei Kornilov <sk(at)zsrv(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: using index or check in ALTER TABLE SET NOT NULL |
Date: | 2017-11-29 16:15:07 |
Message-ID: | 11336.1511972107@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> I did not look at the patch yet, but TBH if it uses SPI for sub-operations
>> of ALTER TABLE I think that is sufficient reason to reject it out of hand.
> You mean like what ALTER TABLE ... ADD FOREIGN KEY does?
Yeah, and if you look at the warts that SPI has grown to support that
usage, you'll see why I'm so unhappy. We should never have allowed
FKs to be built on top of SPI; they require semantics that don't exist
in SQL. I think this would lead to more of the same --- not exactly
the same of course, but more warts. See Robert's nearby musings about
semantics of index null checks for an example.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-11-29 16:50:31 | Re: using index or check in ALTER TABLE SET NOT NULL |
Previous Message | Robert Haas | 2017-11-29 16:00:32 | Re: using index or check in ALTER TABLE SET NOT NULL |