Re: using index or check in ALTER TABLE SET NOT NULL - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: using index or check in ALTER TABLE SET NOT NULL
Date
Msg-id CA+q6zcWfmvu4nsbLfHDtBoBqM+auAQsO2KCqE+kX6d2LzNLg+Q@mail.gmail.com
Whole thread Raw
In response to Re: using index or check in ALTER TABLE SET NOT NULL  (Sergei Kornilov <sk@zsrv.org>)
Responses Re: using index or check in ALTER TABLE SET NOT NULL  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-hackers
>On Sun, 15 Apr 2018 at 09:09, Sergei Kornilov <sk@zsrv.org> wrote:
>
> Attached updated patch follows recent Reorganize partitioning code commit.
> regards, Sergei

This patch went through the last tree commit fests without any noticeable
activity, but cfbot says it still applies and doesn't break any tests. The
patch itself is rather small, the only significant objection I see from the
thread is that probably "SET NOT NULL NOT VALID" feature could be more
appropriate way of fixing the original problem, but looks like no one is
working on that (the only related thread I could found was this one [1]). If
not properly cataloguing NOT NULL constraints would be fixed, can it
potentially conflict with the current patch or not?


[1]: https://www.postgresql.org/message-id/flat/CAASwCXcOokBqHf8BXECbDgOLkXxJyL_Q_twhg2dGWSvgMzz%3DxA%40mail.gmail.com


pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: Optimizing nested ConvertRowtypeExpr execution
Next
From: Erik Rijkers
Date:
Subject: tickling the lesser contributor's withering ego