Re: Table-Level Locks and Transactions

From: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: greg(dot)rychlewski(at)gmail(dot)com, pgsql-novice(at)lists(dot)postgresql(dot)org
Subject: Re: Table-Level Locks and Transactions
Date: 2021-12-09 12:47:47
Message-ID: CANbhV-GA8cZo3toh+m49+_aeU46XUCgQqN5QhDvoKfY+wbbPAg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Thu, 9 Dec 2021 at 11:47, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:

> > Have you thought about using DROP INDEX CONCURRENTLY and CREATE INDEX
> > CONCURRENTLY?
>
> These cannot be used in a transaction, however.

True, but they don't need to be for this case.

If this is the same index, look at REINDEX CONCURRENTLY.

--
Simon Riggs http://www.EnterpriseDB.com/

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Greg Rychlewski 2021-12-10 19:23:50 Streaming Replication Protocol and Logical Replication
Previous Message Laurenz Albe 2021-12-09 11:47:13 Re: Table-Level Locks and Transactions