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

From Andres Freund
Subject Re: Alter index rename concurrently to
Date
Msg-id 20180802204441.4dhfszzfunhyoigp@alap3.anarazel.de
Whole thread Raw
In response to Re: Alter index rename concurrently to  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Alter index rename concurrently to
List pgsql-hackers
Hi,

On 2018-08-02 16:30:42 -0400, Robert Haas wrote:
> With this change, we'd be able to say that new statements will
> definitely see the results of concurrent DDL.

I don't think it really gets you that far. Because you're suggesting to
do it at the parse stage, you suddenly have issues with prepared
statements. Some client libraries, and a lot more frameworks,
automatically use prepared statements when they see the same query text
multiple times.  And this'll not improve anything on that.

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.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: "Write amplification" is made worse by "getting tired" whileinserting into nbtree secondary indexes (Was: Why B-Tree suffix truncation matters)
Next
From: Tom Lane
Date:
Subject: Re: Alter index rename concurrently to