Re: [sqlsmith] Failed assertion in joinrels.c - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [sqlsmith] Failed assertion in joinrels.c
Date
Msg-id CAB7nPqSW-rUBUaECXzi1ZNMpNLdEsDYec=2mWNQ+J4qeGKF2OQ@mail.gmail.com
Whole thread Raw
In response to Re: [sqlsmith] Failed assertion in joinrels.c  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [sqlsmith] Failed assertion in joinrels.c  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Jul 27, 2016 at 5:11 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> Committed with minor kibitizing: you don't need an "else" after a
> statement that transfers control out of the function.

Thanks. Right, I forgot that.

> Shouldn't
> pg_get_function_arguments, pg_get_function_identity_arguments,
> pg_get_function_result, and pg_get_function_arg_default get the same
> treatment?

Changing all of them make sense. Please see attached.

While looking at the series of functions pg_get_*, I have noticed as
well that pg_get_userbyid() returns "unknown (OID=%u)" when it does
not know a user. Perhaps we'd want to change that to NULL for
consistency with the rest?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: to_date_valid()
Next
From: Tom Lane
Date:
Subject: Re: Proposal: revert behavior of IS NULL on row types