<!-- $PostgreSQL: pgsql/doc/src/sgml/regress.sgml,v 1.40 2004/05/21 05:07:55 tgl Exp $ -->

<literal>PST8PDT</literal> (Berkeley, California), and there will be apparent

failures if the tests are not run with that time zone setting.

ensures proper results. However, your operating system must provide

support for the <literal>PST8PDT</literal> time zone, or the time zone-dependent

tests will fail. To verify that your machine does have this

support, type the following:

<screen>

env TZ=PST8PDT date

</screen>

The command above should have returned the current system time in

the <literal>PST8PDT</literal> time zone. If the <literal>PST8PDT</literal> time zone is not available,

then your system may have returned the time in UTC. If the

<literal>PST8PDT</literal> time zone is missing, you can set the time zone

rules explicitly:

<programlisting>

PGTZ='PST8PDT7,M04.01.0,M10.05.03'; export PGTZ

</programlisting>

</para>

<para>

There appear to be some systems that do not accept the

recommended syntax for explicitly setting the local time zone

rules; you may need to use a different <envar>PGTZ</envar>

setting on such machines.

</para>

<para>

Some systems using older time-zone libraries fail to apply

daylight-saving corrections to dates before 1970, causing

pre-1970 <acronym>PDT</acronym> times to be displayed in <acronym>PST</acronym> instead. This will

result in localized differences in the test results.