Bug: century/millenium still broken

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: pgsql-bugs(at)postgreSQL(dot)org
Subject: Bug: century/millenium still broken
Date: 2004-08-09 23:58:07
Message-ID: 21893.1092095887@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

After all that about numbering centuries and millenia correctly,
why does CVS tip still give me

regression=# select extract(century from now());
date_part
-----------
20
(1 row)

[ ... looks in code ... ]

Apparently it's because you fixed only timestamp_part, and not
timestamptz_part. I'm not too sure about what timestamp_trunc or
timestamptz_trunc should do, but they may be wrong as well.

Could we have a more complete patch?

regards, tom lane

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message bpalmer 2004-08-10 01:35:32 PG 8.0.0 on OpenBSD problems
Previous Message Bruce Momjian 2004-08-09 20:39:11 Re: 8.0: Absolute path required for INITDB?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-08-10 00:27:38 Re: Make psql version aware; hide tablespace from older versions
Previous Message Andrew Dunstan 2004-08-09 23:54:47 Re: PITR on Win32 - Archive and Restore