Re: Avoid lost result of recursion (src/backend/optimizer/util/inherit.c)

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Richard Guo <guofenglinux(at)gmail(dot)com>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoid lost result of recursion (src/backend/optimizer/util/inherit.c)
Date: 2022-12-23 03:36:14
Message-ID: CAApHDvoThZcokzxFd4LNLDkxeyfXfar_bmA0bLORDr14e=cL5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 23 Dec 2022 at 16:22, Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> Attached shows a test case I was able to come up with that I can see
> is broken by a61b1f74 though passes after applying Richard's patch.

Thanks for the test case. I'll look at this now.

+UPDATE rootp SET b = b || 'd' RETURNING a, b, c, d;
+ a | b | c | d
+---+------+-----+---
+ 1 | food | 1.1 |

Coding on an empty stomach I see! :)

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-12-23 03:41:48 Re: Perform streaming logical transactions by background workers and parallel apply
Previous Message Amit Langote 2022-12-23 03:29:56 Re: Avoid lost result of recursion (src/backend/optimizer/util/inherit.c)