From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: funkiness with '1999-12-31 19:00:00-05'::timestamp with time zone |
Date: | 2010-09-03 20:14:43 |
Message-ID: | 28949.1283544883@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Josh Kupershmidt <schmiddy(at)gmail(dot)com> writes:
> On Fri, Sep 3, 2010 at 4:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Interesting. I can't imagine how you could have produced these with
>> plain COPY, since that would go through timestamptzin. Was it by any
>> chance a binary COPY? If so I could believe that funny timestamps could
>> get in. Maybe some confusion over endianness of the binary data, for
>> instance.
> Exactly, the code is using COPY ... TO STDOUT WITH BINARY along with
> COPY ... FROM STDIN WITH BINARY.
OK; what you need to look at is how the client code is preparing the
timestamp values. What they should be is floats representing seconds
since 2000-01-01 00:00 GMT, sent in bigendian byte order.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-09-03 20:49:39 | Re: How can I use parameters in plain sql |
Previous Message | Josh Kupershmidt | 2010-09-03 20:10:33 | Re: funkiness with '1999-12-31 19:00:00-05'::timestamp with time zone |