On Fri, Sep 9, 2011 at 5:13 PM, Tom Lane wrote:
>> Yet PostgreSQL
>> shows a value that is exactly 26 minutes behind the others (12:09:40).
>
> You've fat-fingered the to_char usage --- MM is month, not minutes
> (I think you want MI for that).
>
Yep, that's exactly it. Thanks so much for your h
Preston Landers writes:
> SELECT TO_CHAR( TIMESTAMP WITH TIME ZONE 'epoch' + 1315503340 *
> INTERVAL '1 second', 'MM-DD- HH:MM:SS TZ');
> 09-08-2011 12:09:40 CDT
> As you can see, Python, SQL Server, and Oracle all agree that the
> timestamp 1315503340 means 12:35:40 CDT on that date.
So doe
