pg.ddx.io pgsql-hackers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: James Coleman <jtc331@gmail.com>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: remove spurious CREATE INDEX CONCURRENTLY wait
Date: Thu, 11 Nov 2021 09:38:07 -0300
Message-ID: <202111111238.5sql3jupeshe@alvherre.pgsql> (raw)
In-Reply-To: <20211111020724.ggsfhcq3krq5r4hb@alap3.anarazel.de>
On 2021-Nov-10, Andres Freund wrote:
> > Reverts 27838981be9d (some comments are kept). Per discussion, it does
> > not seem safe to relax the lock level used for this; in order for it to
> > be safe, there would have to be memory barriers between the point we set
> > the flag and the point we set the trasaction Xid, which perhaps would
> > not be so bad; but there would also have to be barriers at the readers'
> > side, which from a performance perspective might be bad.
> >
> > Now maybe this analysis is wrong and it *is* safe for some reason, but
> > proof of that is not trivial.
>
> I just noticed that this commit (dcfff74fb16) didn't revert the change of lock
> level in ReplicationSlotRelease(). Was that intentional?
Hmm, no, that seems to have been a mistake. I'll restore it.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"El miedo atento y previsor es la madre de la seguridad" (E. Burke)
view thread (46+ messages) latest in thread
Message-ID: <202111111238.5sql3jupeshe@alvherre.pgsql> Permalink: ../202111111238.5sql3jupeshe@alvherre.pgsql/ Also on: postgresql.org/message-id/202111111238.5sql3jupeshe@alvherre.pgsql ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-hackers@postgresql.org Cc: alvherre@alvh.no-ip.org, andres@anarazel.de, tgl@sss.pgh.pa.us, michael@paquier.xyz, 9erthalion6@gmail.com, jtc331@gmail.com, pgsql-hackers@lists.postgresql.org Subject: Re: remove spurious CREATE INDEX CONCURRENTLY wait In-Reply-To: <202111111238.5sql3jupeshe@alvherre.pgsql> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox