From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 19:52:45 |
Message-ID: | AANLkTimUiEEeRntWcgJAoC3p6ndXBW8fxJ+m4PfyZC5C@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Sep 3, 2010 at 3:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Wow. You must have gotten those with the help of some arithmetic,
> because timestamptzin would never have produced them. I found out I can
> do
>
> regression=# select extract(epoch from ('2000-01-01 00:00:00'::timestamptz + '0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001'::interval) - '2000-01-01 00:00:00');
> date_part
> -----------
> 1e-209
> (1 row)
>
> but I wonder what it was you actually did.
I wonder myself :-) I encountered these timestamps while going through
some C code I inherited which uses libpq to load several tables (such
as myschema.strange_table in the original example) using COPY FROM
STDIN. I don't think any timestamp arithmetic was involved. The code
was supposed to copy in legitimate timestamps, but instead loaded all
these '1999-12-31 19:00:00-05' values, and I'm still trying to figure
out how/why.
Josh
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-03 20:01:11 | Re: funkiness with '1999-12-31 19:00:00-05'::timestamp with time zone |
Previous Message | Tom Lane | 2010-09-03 19:40:37 | Re: funkiness with '1999-12-31 19:00:00-05'::timestamp with time zone |