Re: BUG #7804: timeofday() output string is not compatible with "timestamp with time zone" data type

From: Руслан Измайлов <dotbrat(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7804: timeofday() output string is not compatible with "timestamp with time zone" data type
Date: 2013-01-14 18:38:29
Message-ID: CABoaF20aGtbfLiDUUCNaRB-T9t3d4St_FBeFCx5Zh=CsSQVpnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I need a real-time clock value so I will use clock_timestamp() to get it.
Thanks for the answer.

2013/1/15 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>

> dotbrat(at)gmail(dot)com writes:
> > SET TIME ZONE 'Europe/Minsk';
> > select timeofday()::timestamp with time zone;
> > ERROR: invalid input syntax for type timestamp with time zone: "Mon Jan
> 14
> > 08:18:20.333915 2013 FET"
>
> The issue seems to be that the recently-invented abbreviation FET
> isn't anywhere in our default list of timezone abbreviations.
>
> That probably should be fixed, but in the meantime, you really should be
> aware that timeofday() is deprecated, and there's no reason at all to
> use it in the above manner anyway. now() or current_timestamp are
> simpler and much faster.
>
> regards, tom lane
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message joe 2013-01-14 21:11:08 BUG #7808: unnest doesn't handle nulls in array of composite types correctly
Previous Message Tom Lane 2013-01-14 18:13:32 Re: BUG #7804: timeofday() output string is not compatible with "timestamp with time zone" data type