Re: Row pattern recognition - Mailing list pgsql-hackers

From Henson Choi
Subject Re: Row pattern recognition
Date
Msg-id CAAAe_zAjkjUZHMqu5DjgZH9ZZ6D5v4bBJy60ziwhHRoohnB7Zg@mail.gmail.com
Whole thread
In response to Re: Row pattern recognition  (jian he <jian.universality@gmail.com>)
Responses Re: Row pattern recognition
List pgsql-hackers
Hi jian,

Thanks -- this is a clean improvement, no objections. Honestly this part of the
parser is an area where you read it better than I do, so I'm glad to defer to
you here. Quick notes inline.

> The above comments can be deleted, ParseRPRNavCall, ParseFuncOrColumn
> already have lots of comments.
> Also the error check and its message are quite intuitive in ParseRPRNavCall.

Agreed.

> So, I tended to use coerce_to_target_type.

Agreed.

> ParseRPRNavCall ending can be simplified because coerce_to_target_type
> can handle the same data type.
> Therefore, `if (offtype != INT8OID)` is not necessary.

Agreed.

> Drop the extra parentheses around ereport() argument lists, fewer
> parentheses are always better for new code.

Agreed.

Tatsuo, this one looks good to take whenever you like.

Best,
Henson

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Fix publisher-side sequence permission reporting
Next
From: Chao Li
Date:
Subject: Re: bytea(uuid) missing proleakproof?