timezone mismatch

If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to pgsql-ports(at)postgresql(dot)org(dot)

To report any other bug, fill out the form below and e-mail it to
pgsql-bugs(at)postgresql(dot)org(dot)

If you not only found the problem but solved it and generated a patch
then e-mail it to pgsql-patches(at)postgresql(dot)org instead. Please use the
command "diff -c" to generate the patch.

You may also enter a bug report at http://www.postgresql.org/ instead of
e-mail-ing this form.

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Philip Guenther
Your email address : guenther(at)gac(dot)edu

System Configuration
---------------------
Architecture (example: Intel Pentium) : sun4u (Sun UltraSPARC-II)

Operating System (example: Linux 2.0.26 ELF) : Solaris 7

PostgreSQL version (example: PostgreSQL-6.5.1): PostgreSQL-6.5.1

Compiler used (example: gcc 2.8.0) : SunPRO cc 4.2

Please enter a FULL description of your problem:
------------------------------------------------

The regression tests use a timezone that experiences Daylight Savings
Time. While the regression scripts set the timezone to PST8PDT, if the
regression suite is run while daylight saving would be in effect in
that timezone, all the time tests 'fail' because all the time & date
values are reported as being in the PDT timezone instead of the PST
timezone. For example, here is the first chunk of one diff from a
run of the regression suite.

*** expected/abstime.out Sun Jan 4 21:35:19 1998
--- results/abstime.out Thu Aug 19 22:40:55 1999
***************
*** 22,28 ****
|current
|infinity
|-infinity
! |Sat May 10 23:59:12 1947 PST
|invalid
(8 rows)

--- 22,28 ----
|current
|infinity
|-infinity
! |Sat May 10 23:59:12 1947 PDT
|invalid
(8 rows)

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------

Running the regression tests (and generating new expected results) with
the timezone set to some zone that doesn't experience daylight savings
time should fix it.