Bug: century/millenium still broken - Mailing list pgsql-bugs

From Tom Lane
Subject Bug: century/millenium still broken
Date
Msg-id 21893.1092095887@sss.pgh.pa.us
Whole thread Raw
Responses Re: Bug: century/millenium still broken
List pgsql-bugs
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

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: 8.0: Absolute path required for INITDB?
Next
From: Mike G
Date:
Subject: beta - win32, restore from pg_dump not possible