Re: problem with RETURNING and update row movement
От | Amit Langote |
---|---|
Тема | Re: problem with RETURNING and update row movement |
Дата | |
Msg-id | CA+HiwqHTxzx+aHU+cvkzm8cjXvEK9K-G6b8UoTm2Sx0ADVQeFA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: problem with RETURNING and update row movement (Amit Langote <amitlangote09@gmail.com>) |
Ответы |
Re: problem with RETURNING and update row movement
|
Список | pgsql-hackers |
On Thu, Sep 24, 2020 at 2:26 PM Amit Langote <amitlangote09@gmail.com> wrote: > On Thu, Sep 24, 2020 at 1:54 PM Michael Paquier <michael@paquier.xyz> wrote: > > On Thu, Sep 24, 2020 at 04:25:24AM +0900, Etsuro Fujita wrote: > > > Sorry, my thought was vague. To store xmin/xmax/cmin/cmax into a > > > given slot, we need to extend the TupleTableSlot struct to contain > > > these attributes as well? Or we need to introduce a new callback > > > routine for that (say, setsysattr)? These would not be > > > back-patchable, though. > > > > Please note that the latest patch fails to apply, so this needs a > > rebase. > > I saw the CF-bot failure too yesterday, although it seems that it's > because the bot is trying to apply the patch version meant for v11 > branch onto HEAD branch. I just checked that the patches apply > cleanly to their respective branches. I checked that the last statement is still true, so I've switched the status back to Needs Review. -- Amit Langote EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: