| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Douglas Doole <dougdoole(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Inconsistencies in from_char_parse_int_len() |
| Date: | 2017-07-31 20:57:53 |
| Message-ID: | 18481.1501534673@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Douglas Doole <dougdoole(at)gmail(dot)com> writes:
> I was playing with TO_TIMESTAMP() and I noticed a weird result:
> postgres=# select to_timestamp('20170-07-24 21:59:57.12345678', 'yyyy-mm-dd
> hh24:mi:ss.us');
> to_timestamp
> --------------------------------
> 20170-07-24 22:00:09.345678+00
> (1 row)
FWIW, we already tightened that up in v10:
regression=# select to_timestamp('20170-07-24 21:59:57.12345678', 'yyyy-mm-dd hh24:mi:ss.us');
ERROR: date/time field value out of range: "20170-07-24 21:59:57.12345678"
There may well be some discrepancies left.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-07-31 21:08:44 | Re: POC: Sharing record typmods between backends |
| Previous Message | Tom Lane | 2017-07-31 20:54:45 | Re: PL_stashcache, or, what's our minimum Perl version? |