Re: executor relation handling - Mailing list pgsql-hackers

From David Rowley
Subject Re: executor relation handling
Date
Msg-id CAKJS1f8uCk937hbTN5Fud+etubv5mczhguwabgaqQ_qr_Woe7A@mail.gmail.com
Whole thread Raw
In response to Re: executor relation handling  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: executor relation handling  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 29 September 2018 at 03:49, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> On 2018-Sep-28, Amit Langote wrote:
>> On 2018/09/28 17:48, David Rowley wrote:
>
>> > 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
>>
>> Oops, good catch that one.  Removed "InitPlan: " from the message in the
>> attached.
>
> Were there two cases of that?  Because one still remains.

Yeah, 0001 added it and 0004 removed it again replacing it with the
corrected version.

I've attached v10 which fixes this and aligns the WARNING text in
ExecInitRangeTable() and addRangeTableEntryForRelation().

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

Attachment

pgsql-hackers by date:

Previous
From: Don Seiler
Date:
Subject: Re: [PATCH] Include application_name in "connection authorized" log message
Next
From: Mark Wong
Date:
Subject: Re: Odd 9.4, 9.3 buildfarm failure on s390x