Re: crypt function crash on postgresql 9.3.20 and 10 - Mailing list pgsql-bugs

From Michael
Subject Re: crypt function crash on postgresql 9.3.20 and 10
Date
Msg-id 20180202220545.12ec535f@ahpeb
Whole thread Raw
In response to Re: crypt function crash on postgresql 9.3.20 and 10  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
В Fri, 2 Feb 2018 11:53:06 -0700
"David G. Johnston" <david.g.johnston@gmail.com> пишет:

> On Friday, February 2, 2018, Michael <asper@tagan.ru> wrote:
>
> >
> > However, in a postgresql 9.3.2, such a call does not lead to an
> > error.
>
>
> If you are saying 9.3.2 gives a result and 9.3.20 raises an error I
> suspect the response in 9.3.2 was bogus and giving an error instead
> of a bogus result was deemed the best fix.
>
>
> > how then should the function respond to a call
> > select crypt('123',NULL);
> > this does not cause an error
> >
>
> It probably returns null because I would hope the function is defined
> as strict.
>
> David J.

Thank you for the clarification. In any case, I've already fixed the
queries in my application to get around this behavior.


pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: crypt function crash on postgresql 9.3.20 and 10
Next
From: Peter Eisentraut
Date:
Subject: Re: BUG #14952: COPY fails to fill in IDENTITY column default value