Hi! Recently, we switched from Pg 8.3 to Pg 9.1, using Pg9's pg_upgrade to migrate our cluster. The cluster itself is running on a Debian 6 machine with timezone Europe/Berlin, which means UTC+02 currently.
Under Pg 8.3, we used the timestamp 0001-01-01 00:00:00+01 as an easy-to-remember marker for 'dunno, but predates any usual business dates' for fields of type timestamp with time zone. With Pg 9.1, these timestamps now appear as 0001-12-31 23:53:28+00:53:28 BC (using a current psql shell in both cases). If I try to reset the timestamp, eg by update testtable set ts='0001-01-01'; the result is 0001-01-01 00:00:00+00:53:28 Specifying the time explicitly update testtable set ts='0001-01-01 00:00:00+01:00:00'; results in 0001-12-31 23:53:28+00:53:28 BC again, hence I'd suspect that somehow the textual representation of such timestamps is broken?! Any ideas? Is this a known bug (I didn't find), maybe fixed in 9.2? Karsten -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
