Re: Alter index rename concurrently to

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Alter index rename concurrently to
Дата
Msg-id 20180802204441.4dhfszzfunhyoigp@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: Alter index rename concurrently to  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Alter index rename concurrently to  (Robert Haas <robertmhaas@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: "Write amplification" is made worse by "getting tired" whileinserting into nbtree secondary indexes (Was: Why B-Tree suffix truncation matters)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Alter index rename concurrently to