| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Michael <asper(at)tagan(dot)ru> |
| Cc: | Rainer Pruy <Rainer(dot)Pruy(at)acrys(dot)com>, Pavan Teja <pavan(dot)postgresdba(at)gmail(dot)com>, Mike Porter <mike(at)udel(dot)edu>, Postgres Bug <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: crypt function crash on postgresql 9.3.20 and 10 |
| Date: | 2018-02-02 18:53:06 |
| Message-ID: | CAKFQuwa3uBiXhr=bCdb1NGDC8BHJU70zgKoncmXiP3=6ZqzRNA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Friday, February 2, 2018, Michael <asper(at)tagan(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael | 2018-02-02 19:05:45 | Re: crypt function crash on postgresql 9.3.20 and 10 |
| Previous Message | Michael | 2018-02-02 18:47:46 | Re: crypt function crash on postgresql 9.3.20 and 10 |