| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-14 06:44:46 |
| Message-ID: | 3284df7c-32dd-1a13-54ad-f5c76d21d49f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/08/2018 15:00, Robert Haas wrote:
> On Thu, Aug 2, 2018 at 4:44 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> ISTM, if you want to increase consistency in this area, you've to go
>> further. E.g. processing invalidations in StartTransactionCommand() in
>> all states, which'd give you a lot more consistency.
>
> Hmm, that seems like a pretty good idea.
That would only affect top-level commands, not things like SPI. Is that
what we want? Or we could sprinkle additional
AcceptInvalidationMessages() calls in spi.c.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-08-14 07:04:54 | Re: Alter index rename concurrently to |
| Previous Message | Peter Eisentraut | 2018-08-14 06:33:26 | Re: Alter index rename concurrently to |