| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, 'Andreas Karlsson *EXTERN*' <andreas(at)proxel(dot)se>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: to_date_valid() |
| Date: | 2016-07-27 01:25:33 |
| Message-ID: | b28373f4-7e37-3bc4-25a5-65aef4006cf0@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/5/16 4:24 AM, Albe Laurenz wrote:
> But notwithstanding your feeling that you would like your application
> to break if it makes use of this behaviour, it is a change that might
> make some people pretty unhappy - nobody can tell how many.
What is the use of the existing behavior? You get back an arbitrary
implementation dependent value. We don't even guarantee what the value
will be. If we changed it to return a different implementation
dependent value, would users get upset?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-07-27 01:27:02 | Re: [sqlsmith] Failed assertion in joinrels.c |
| Previous Message | Vik Fearing | 2016-07-27 01:24:28 | Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE |