Re: pointless check in RelationBuildPartitionDesc - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pointless check in RelationBuildPartitionDesc
Date
Msg-id 20180905130557.4spqs67cq7jdhoq4@alvherre.pgsql
Whole thread Raw
In response to Re: pointless check in RelationBuildPartitionDesc  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On 2018-Sep-05, Amit Langote wrote:

> On 2018/09/05 1:50, Alvaro Herrera wrote:
> > Proposed patch.  Checking isnull in a elog(ERROR) is important, because
> > the column is not marked NOT NULL.  This is not true for other columns
> > where we simply do Assert(!isnull).
> 
> Looks good.  Thanks for taking care of other sites as well.
> 
> @@ -14705,7 +14705,9 @@ ATExecDetachPartition(Relation rel, RangeVar *name)
> 
>      (void) SysCacheGetAttr(RELOID, tuple, Anum_pg_class_relpartbound,
>                             &isnull);
> -    Assert(!isnull);
> +    if (isnull)
> +        elog(ERROR, "null relpartbound for relation %u",
> +             RelationGetRelid(partRel));
> 
> In retrospect, I'm not sure why this piece of code is here at all; maybe
> just remove the SycCacheGetAttr and Assert?

Yeah, good idea, will do.

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


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: [HACKERS] Bug in to_timestamp().
Next
From: Tom Lane
Date:
Subject: Re: Bug fix for glibc broke freebsd build in REL_11_STABLE