From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Obsolete comment in partbounds.c |
Date: | 2019-10-21 08:44:25 |
Message-ID: | CAPmGK16syixbm8vLfx-+L8QAzGe_rq5YQvjPJAKRKEO+wFhokQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Oct 19, 2019 at 5:56 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
> On Fri, Oct 18, 2019 at 6:56 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> > On 2019-Oct-18, Etsuro Fujita wrote:
> > > While reviewing the partitionwise-join patch, I noticed $Subject,ie,
> > > this in create_list_bounds():
> > >
> > > /*
> > > * Never put a null into the values array, flag instead for
> > > * the code further down below where we construct the actual
> > > * relcache struct.
> > > */
> > > if (null_index != -1)
> > > elog(ERROR, "found null more than once");
> > > null_index = i;
> > >
> > > "the code further down below where we construct the actual relcache
> > > struct" isn't in the same file anymore by refactoring by commit
> > > b52b7dc25. How about modifying it like the attached?
> >
> > Yeah, agreed. Instead of "the null comes from" I would use "the
> > partition that stores nulls".
>
> I think your wording is better than mine. Thank you for reviewing!
I applied the patch down to PG12.
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2019-10-21 08:44:43 | Re: dropdb --force |
Previous Message | Amit Kapila | 2019-10-21 08:28:00 | Re: Fix comment in XLogFileInit() |