Horton

Re: Alter index rename concurrently to

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Andrey Klychkov <aaklychkov@mail.ru>, Victor Yegorov <vyegorov@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2018-08-02T20:29:36Z
Lists: pgsql-hackers 
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Aug 1, 2018 at 3:36 PM, Andres Freund <andres@anarazel.de> wrote:
>> What precisely are you proposing?

> Inserting AcceptInvalidationMessages() in some location that
> guarantees it will be executed at least once per SQL statement.  I
> tentatively propose the beginning of parse_analyze(), but I am open to
> suggestions.

What will that accomplish that the existing call in transaction start
doesn't?  It might make the window for concurrency issues a bit narrower,
but it certainly doesn't close it.

			regards, tom lane

Commits

  1. Lower lock level for renaming indexes