Re: [HACKERS] close_ps, NULLs, and DirectFunctionCall - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] close_ps, NULLs, and DirectFunctionCall
Date
Msg-id CA+TgmobrSXOSUtjpAQ=p3M0SN3s0gaMiF23=fRb54e2UFWC4TQ@mail.gmail.com
Whole thread Raw
In response to [HACKERS] close_ps, NULLs, and DirectFunctionCall  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
On Wed, Sep 20, 2017 at 4:25 PM, Andrew Gierth
<andrew@tao11.riddles.org.uk> wrote:
> postgres=# select point(1,2) ## '((0,0),(NaN,NaN))'::box;
> ERROR:  function 0x9c5de0 returned NULL
>
> postgres=# select point(1,2) <-> '((0,0),(NaN,NaN))'::box;
> ERROR:  function 0x9c5de0 returned NULL
>
> This seems ... unhelpful (though it's at least better than crashing) and
> inconsistent.

I'd call that a bug.

> The most consistent fix would seem
> to be to make all the affected functions return NULL,

Based on your description of the problem I would tend to agree,
although I'm not really familiar with this area.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] ICU locales and text/char(n) SortSupport on Windows
Next
From: Melanie Plageman
Date:
Subject: Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.