| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org,Stephen Frost <sfrost(at)snowman(dot)net>,Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"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:55:02 |
| Message-ID: | 900056D1-32DF-4927-8251-3E0C0DC407FD@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On November 29, 2017 8:50:31 AM PST, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>As for conflicting snapshots, isn't the lock we're taking already
>AccessExclusive..?
Doesn't help if e.g. the current xact is repeatable read or if your own xact deleted things (other xacts with snapshots could still see null rows, despite new take definition).
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shubham Barai | 2017-11-29 17:50:36 | Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index |
| Previous Message | Sergei Kornilov | 2017-11-29 16:53:01 | Re: using index or check in ALTER TABLE SET NOT NULL |