Re[2]: Alter index rename concurrently to

From: Andrey Klychkov <aaklychkov(at)mail(dot)ru>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Victor Yegorov <vyegorov(at)gmail(dot)com>
Subject: Re[2]: Alter index rename concurrently to
Date: 2018-07-18 09:44:30
Message-ID: 1531907070.621013080@f382.i.mail.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>Среда, 18 июля 2018, 12:21 +03:00 от Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>:
>
>If we think the lower lock level is OK, then we should just use
>it always.
>
Hi, I absolutely agree with you.
If lower locking is safe and possible to be used by default in renaming it will be great.
What stage is solving of this issue? Does anybody do it?

Thank you!

--
Kind regards,
Andrey Klychkov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2018-07-18 10:23:39 Re: Speeding up INSERTs and UPDATEs to partitioned tables
Previous Message Kato, Sho 2018-07-18 09:44:29 RE: Speeding up INSERTs and UPDATEs to partitioned tables