| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | sk(at)zsrv(dot)org |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, alvherre(at)alvh(dot)no-ip(dot)org, Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, i(dot)musin(at)postgrespro(dot)ru, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: using index or check in ALTER TABLE SET NOT NULL |
| Date: | 2018-11-04 14:18:20 |
| Message-ID: | CA+q6zcWfmvu4nsbLfHDtBoBqM+auAQsO2KCqE+kX6d2LzNLg+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>On Sun, 15 Apr 2018 at 09:09, Sergei Kornilov <sk(at)zsrv(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2018-11-04 14:38:47 | tickling the lesser contributor's withering ego |
| Previous Message | Dmitry Dolgov | 2018-11-04 13:10:05 | Re: Optimizing nested ConvertRowtypeExpr execution |