Re: REINDEX CONCURRENTLY unexpectedly fails

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: REINDEX CONCURRENTLY unexpectedly fails
Дата
Msg-id 20191114080855.GG1910@paquier.xyz
обсуждение исходный текст
Ответ на Re: REINDEX CONCURRENTLY unexpectedly fails  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: REINDEX CONCURRENTLY unexpectedly fails  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Дерево обсуждения 
On Wed, Nov 13, 2019 at 11:45:34AM -0500, Tom Lane wrote:
> Oh, I like that idea.  Keeps applications from having to think
> about this.

That's interesting, but I would be on the side of just generating an
error in this case thinking about potential future features like
global temporary tables, and because it could always be relaxed in the
future.

I am actually wondering if we don't have more problems with other
utility commands which spawn multiple transactions...

Any extra opinion?
--
Michael
Вложения

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Unexpected "cache lookup failed for collation 0" failure
Следующее
От: "Fan||"
Дата:
Сообщение: 回复： BUG #16102: Table can't be drop on PostgreSQL 10.09 if the table was created from PostgreSQL 10.10