From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andrey Klychkov <aaklychkov(at)mail(dot)ru>, Victor Yegorov <vyegorov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Alter index rename concurrently to |
Date: | 2018-08-02 20:29:36 |
Message-ID: | 5607.1533241776@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Aug 1, 2018 at 3:36 PM, Andres Freund <andres(at)anarazel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-08-02 20:30:42 | Re: Alter index rename concurrently to |
Previous Message | Tom Lane | 2018-08-02 20:25:19 | Re: Expression errors with "FOR UPDATE" and postgres_fdw with partition wise join enabled. |