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

From Robert Haas
Subject Re: Alter index rename concurrently to
Date
Msg-id CA+TgmoZ6vjMjQmzbpQkLBB9iY03SBx+gWHpsgwpyjzQAoZ3nrw@mail.gmail.com
Whole thread Raw
In response to Re: Alter index rename concurrently to  (Andres Freund <andres@anarazel.de>)
Responses Re: Alter index rename concurrently to
Re: Alter index rename concurrently to
List pgsql-hackers
On Wed, Aug 1, 2018 at 3:36 PM, Andres Freund <andres@anarazel.de> wrote:
>> Right.  If nobody sees a reason not to change that, I think we should.
>> It would make the behavior more predictable with, I hope, no real
>> loss.
>
> 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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: FailedAssertion on partprune
Next
From: Andres Freund
Date:
Subject: Re: Alter index rename concurrently to