Building 8.4 on a client's system, I get a regression failure apparently
due to some difference between the system's timezone DB and what out
regression tests expect, as shown below.
I'm wondering if we should not disable the timestamptz regression test
when we configure with the system timezone db. I guess i could patch the
SRPM by providing an alternative result file - not sure if it's worth it
though.
cheers
andrew
***
/usr/local/src/rpms/BUILD/postgresql-8.4.0/src/test/regress/expected/timestamptz.out
2009-03-21 21:12:32.000000000 -0400
---
/usr/local/src/rpms/BUILD/postgresql-8.4.0/src/test/regress/results/timestamptz.out
2009-07-28 12:33:15.000000000 -0400
***************
*** 153,159 ****
SELECT '20500710 173201 Europe/Helsinki'::timestamptz; -- DST
timestamptz
------------------------------
! Sun Jul 10 07:32:01 2050 PDT
(1 row)
SELECT '20500110 173201 Europe/Helsinki'::timestamptz; -- non-DST
--- 153,159 ----
SELECT '20500710 173201 Europe/Helsinki'::timestamptz; -- DST
timestamptz
------------------------------
! Sun Jul 10 07:32:01 2050 PST
(1 row)
SELECT '20500110 173201 Europe/Helsinki'::timestamptz; -- non-DST
***************
*** 165,171 ****
SELECT '205000-07-10 17:32:01 Europe/Helsinki'::timestamptz; -- DST
timestamptz
--------------------------------
! Thu Jul 10 07:32:01 205000 PDT
(1 row)
SELECT '205000-01-10 17:32:01 Europe/Helsinki'::timestamptz; -- non-DST
--- 165,171 ----
SELECT '205000-07-10 17:32:01 Europe/Helsinki'::timestamptz; -- DST
timestamptz
--------------------------------
! Thu Jul 10 07:32:01 205000 PST
(1 row)
SELECT '205000-01-10 17:32:01 Europe/Helsinki'::timestamptz; -- non-DST
======================================================================
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
