Re: problem with RETURNING and update row movement

Поиск
Список
Период
Сортировка
От Amit Langote
Тема Re: problem with RETURNING and update row movement
Дата
Msg-id CA+HiwqFqhQtKDvXFirBFOZoEQJRLHAD=--M4_wrV3HwWfGie-Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: problem with RETURNING and update row movement  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Ответы Re: problem with RETURNING and update row movement  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Sat, Mar 6, 2021 at 12:52 AM David Steele <david@pgmasters.net> wrote:
> On 10/30/20 6:00 AM, Amit Langote wrote:
> > The question
> > I guess is whether that thread must conclude before the fix here can
> > be committed.
>
> Indeed. But it seems like there is a candidate patch on [1] though that
> thread has also stalled. I'll try to get some status on that thread but
> the question remains if this patch will be stalled until [1] is resolved.

Sorry for the delay in following up on this thread.  I've posted new
patches on the other.

FWIW, I think we should go ahead and apply the patches for the bug
reported here.  Anyone who tries to project an updated tuple's system
columns using RETURNING are likely to face problems one way or
another, especially if they have partitioned tables containing
partitions of varying table AMs, but at least they won't face the bug
discussed here.

I've attached patches for all affected branches.

-- 
Amit Langote
EDB: http://www.enterprisedb.com

Вложения

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

Предыдущее
От: Amul Sul
Дата:
Сообщение: Re: [CLOBBER_CACHE]Server crashed with segfault 11 while executing clusterdb
Следующее
От: Juan José Santamaría Flecha
Дата:
Сообщение: Re: [PATCH] Bug fix in initdb output