From: | Michael <asper(at)tagan(dot)ru> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
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 19:05:45 |
Message-ID: | 20180202220545.12ec535f@ahpeb |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
В Fri, 2 Feb 2018 11:53:06 -0700
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> пишет:
> 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.
Thank you for the clarification. In any case, I've already fixed the
queries in my application to get around this behavior.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-02-02 20:15:23 | Re: BUG #14952: COPY fails to fill in IDENTITY column default value |
Previous Message | David G. Johnston | 2018-02-02 18:53:06 | Re: crypt function crash on postgresql 9.3.20 and 10 |