| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
| Cc: | 甄明洋 <zhenmingyang(at)yeah(dot)net>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] Re: [BUGS] Return value error of‘to_timestamp’ |
| Date: | 2016-08-04 15:06:40 |
| Message-ID: | CAKFQuwa1eWdO-7Y-uqRTGrdwj0H=N6iz5dLohLy7BCeLG3=qrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Aug 4, 2016 at 11:03 AM, Aleksander Alekseev <
a(dot)alekseev(at)postgrespro(dot)ru> wrote:
> >> postgres=# select to_timestamp('1990-1-1 11:11:11.123456789',
> >> 'YYYY-MM-DD HH24:MI:SS.US'); to_timestamp
> >> -------------------------------
> >> 1990-01-01 11:13:14.456789+08
> >> (1 row)
> >> postgres=#
>
> > Working as designed...
>
> Maybe it means that current design is poor. However since this behavior
> is documented there are users who might depend on it. So I doubt it
> will be changed any time soon.
>
> Though I wonder maybe we should consider introducing a new set of
> time-related procedures with different behavior (to_timestamp_strict?),
> that would be more obvious to users.
>
Discussions ongoing...
an archive search should be fruitful.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | marko | 2016-08-04 19:17:57 | BUG #14279: Logical decoding misses a transaction completely |
| Previous Message | Aleksander Alekseev | 2016-08-04 15:03:09 | Re: Re: [BUGS] Return value error of‘to_timestamp’ |