Skip site navigation (1) Skip section navigation (2)

Re: timestamp format bug

From: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: timestamp format bug
Date: 2008-01-31 18:45:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> -----Original Message-----
> From: Kevin Grittner [mailto:Kevin(dot)Grittner(at)wicourts(dot)gov]
> Sent: Thursday, January 31, 2008 12:33 PM
> To: Roberts, Jon; pgsql-hackers(at)postgresql(dot)org
> Subject: RE: [HACKERS] timestamp format bug
> >>> On Thu, Jan 31, 2008 at 12:28 PM, in message
> <1A6E6D554222284AB25ABE3229A92762715525(at)nrtexcus702(dot)int(dot)asurion(dot)com>,
> "Roberts,
> Jon" <Jon(dot)Roberts(at)asurion(dot)com> wrote:
> > The default timestamp format appears to be yyyy-mm-dd
> Not to me:
> select now();
>               now
> -------------------------------
>  2008-01-31 12:31:40.568746-06
> (1 row)

I'm guessing that is a server setting on how to format a timestamp.
Your appears to be yyyy-mm-dd  

So on your db, run this query:
select sub.t1, to_char(t1, 'yyyy-mm-dd') as char_t1
select timestamp'2008-01-31 12:31:40.500000' as t1
) sub

I bet you get this:
"2008-01-31 12:31:40.50";"2008-01-31 12:31:40.500000"

Don't you think it should have two identical columns?

Secondly, this link shows that ms should be 000-999 and us should be

All of the other fields are padded like month, day, year, hour, minute,
and second and are consistent.  The formats ms and us should be
consistent too.


In response to


pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2008-01-31 19:47:06
Subject: Re: timestamp format bug
Previous:From: Kevin GrittnerDate: 2008-01-31 18:45:26
Subject: Re: timestamp format bug

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group