Re: Obsolete comment in partbounds.c - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Obsolete comment in partbounds.c
Date
Msg-id 20191018095636.GA25576@alvherre.pgsql
Whole thread Raw
In response to Obsolete comment in partbounds.c  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Responses Re: Obsolete comment in partbounds.c
List pgsql-hackers
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".

While reviewing your patch I noticed a few places where we use an odd
pattern in switches, which can be simplified as shown here.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Partitioning versus autovacuum
Next
From: Craig Ringer
Date:
Subject: Re: [PATCH] Race condition in logical walsender causes longpostgresql shutdown delay