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

From David G. Johnston
Subject Re: crypt function crash on postgresql 9.3.20 and 10
Date
Msg-id CAKFQuwa3uBiXhr=bCdb1NGDC8BHJU70zgKoncmXiP3=6ZqzRNA@mail.gmail.com
Whole thread Raw
In response to crypt function crash on postgresql 9.3.20 and 10  (Михаил Манерко <asper@tagan.ru>)
Responses Re: crypt function crash on postgresql 9.3.20 and 10  (Michael <asper@tagan.ru>)
Re: crypt function crash on postgresql 9.3.20 and 10  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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.

pgsql-bugs by date:

Previous
From: Michael
Date:
Subject: Re: crypt function crash on postgresql 9.3.20 and 10
Next
From: Michael
Date:
Subject: Re: crypt function crash on postgresql 9.3.20 and 10