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

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: 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 02:21:14
Message-ID: CAMbWs4-cnPkfA6YBp8v-8Nf3r6T+rvUm_BSYqqWdhK1J2fgTOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 22, 2022 at 5:22 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:

> On Thu, 22 Dec 2022 at 21:18, Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> > My best guess is that this function is intended to share the same code
> > pattern as in adjust_appendrel_attrs_multilevel. The recursion is
> > needed as 'rel' can be more than one inheritance level below the top
> > parent. I think we can keep the recursion, as in other similar
> > functions, as long as we make it right, as in attached patch.
>
> I still think we should have a test to ensure this is actually
> working. Do you want to write one?

I agree that we should have a test. According to the code coverage
report, the recursion part of this function is never tested. I will
have a try to see if I can come up with a proper test case.

Thanks
Richard

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2022-12-23 02:21:54 Re: Exit walsender before confirming remote flush in logical replication
Previous Message Justin Pryzby 2022-12-23 01:08:18 Re: Small miscellaneus fixes (Part II)