Re: executor relation handling - Mailing list pgsql-hackers

From David Rowley
Subject Re: executor relation handling
Date
Msg-id CAKJS1f_JJY3hk6QXMxkO68uBZQ_iiT0dkZmO-Jj8x_vqjaThdA@mail.gmail.com
Whole thread Raw
In response to Re: executor relation handling  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: executor relation handling  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On 28 September 2018 at 20:28, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
> On 2018/09/28 17:21, David Rowley wrote:
>> I think we maybe should switch the word "assert" for "verifies". The
>> Assert is just checking we didn't get a NoLock and I don't think
>> you're using "assert" meaning the Assert() marco, so likely should be
>> changed to avoid confusion.
>
> Okay, I've revised the text in the attached updated patch.

Meh, I just noticed that the WARNING text claims "InitPlan" is the
function name. I think it's best to get rid of that. It's pretty much
redundant anyway if you do: \set VERBOSITY verbose

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: "Yamaji, Ryo"
Date:
Subject: RE: [HACKERS] Cached plans and statement generalization
Next
From: Amit Langote
Date:
Subject: Re: executor relation handling