Re: ANALYZE: ERROR: tuple already updated by self

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: ANALYZE: ERROR: tuple already updated by self
Дата
Msg-id 20190729045320.ffwc7seez6nbmfaj@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: ANALYZE: ERROR: tuple already updated by self  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Ответы Re: ANALYZE: ERROR: tuple already updated by self  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Список pgsql-hackers
Hi,

On 2019-07-28 21:21:51 +0200, Tomas Vondra wrote:
> AFAICS it applies to 10+ versions, because that's where extended stats
> were introduced. We certainly can't mess with catalogs there, so this is
> about the only backpatchable fix I can think of.

AFAIU the inh version wouldn't be used anyway, and this has never
worked. So I think it's imo fine to fix it that way for < master. For
master we should have something better, even if perhaps not immediately.

- Andres



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

Предыдущее
От: Ashutosh Sharma
Дата:
Сообщение: Re: COPY command on a table column marked as GENERATED ALWAYS
Следующее
От: Fabien COELHO
Дата:
Сообщение: Re: refactoring - share str2*int64 functions