Re: Obsolete comment in partbounds.c

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Obsolete comment in partbounds.c
Date: 2019-10-18 09:56:36
Message-ID: 20191018095636.GA25576@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
simplify-returns.patch text/x-diff 1.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2019-10-18 10:14:59 Re: [PATCH] Race condition in logical walsender causes long postgresql shutdown delay
Previous Message Greg Stark 2019-10-18 09:21:52 Re: Partitioning versus autovacuum