Postgres Pro
Downloads
Home   >   mailing lists

Re[2]: Alter index rename concurrently to - Mailing list pgsql-hackers

From Andrey Klychkov
Subject Re[2]: Alter index rename concurrently to
Date
Msg-id 1531907070.621013080@f382.i.mail.ru
Whole thread Raw
In response to Re: Alter index rename concurrently to  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Alter index rename concurrently to  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view

Среда, 18 июля 2018, 12:21 +03:00 от Peter Eisentraut <peter.eisentraut@2ndquadrant.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

pgsql-hackers by date:

Previous
From: "Kato, Sho"
Date:
Subject: RE: Speeding up INSERTs and UPDATEs to partitioned tables
Next
From: David Rowley
Date:
Subject: Re: Speeding up INSERTs and UPDATEs to partitioned tables