Re: Update comment in ExecPartitionCheck

From: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Update comment in ExecPartitionCheck
Date: 2017-07-06 06:58:40
Message-ID: f419c1b0-6380-d2e8-6b81-269b0085add7@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2017/07/04 18:15, Amit Langote wrote:
> On 2017/07/04 17:55, Etsuro Fujita wrote:
>> This comment in an error handling in ExecPartitionCheck():
>>
>> if (!ExecCheck(resultRelInfo->ri_PartitionCheckExpr, econtext))
>> {
>> char *val_desc;
>> Relation orig_rel = rel;
>>
>> /* See the comment above. */
>> if (resultRelInfo->ri_PartitionRoot)
>>
>> should be updated because we don't have any comment on that above in the
>> code. Since we have a comment on that in ExecConstraints() defined just
>> below that function, I think the comment should be something like this:
>> "See the comment in ExecConstraints().". Attached is a patch for that.
>
> Thanks for fixing that. I forgot to do the same in the patch that got
> committed as 15ce775faa428 [1], which moved that code block from
> ExecConstraints() to ExecPartitionCheck().

Thanks for the explanation!

In relation to this, I found odd behavior in the error handling. Since
that is another topic, I'll start a new thread.

Best regards,
Etsuro Fujita

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2017-07-06 07:06:04 Oddity in error handling of constraint violation in ExecConstraints for partitioned tables
Previous Message Beena Emerson 2017-07-06 06:34:12 Re: increasing the default WAL segment size