Re: remove spurious CREATE INDEX CONCURRENTLY wait

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, James Coleman <jtc331(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: remove spurious CREATE INDEX CONCURRENTLY wait
Date: 2021-11-11 19:50:17
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2021-11-11 09:38:07 -0300, Alvaro Herrera wrote:
> > 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.


In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2021-11-11 20:02:09 JIT doing duplicative optimization?
Previous Message Andres Freund 2021-11-11 19:50:00 Re: Interrupts vs signals