Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit af3487e

Browse files
committed
Update now-obsolete example of platform-specific regression comparison
files.
1 parent bf51b86 commit af3487e

File tree

1 file changed

+21
-28
lines changed

1 file changed

+21
-28
lines changed

doc/src/sgml/regress.sgml

Lines changed: 21 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/regress.sgml,v 1.17 2001/03/20 00:09:36 tgl Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/regress.sgml,v 1.18 2001/08/06 22:53:26 tgl Exp $ -->
22

33
<chapter id="regress">
44
<title id="regress-title">Regression Tests</title>
@@ -49,7 +49,7 @@
4949
<screen>
5050
<computeroutput>
5151
======================
52-
All 76 tests passed.
52+
All 77 tests passed.
5353
======================
5454
</computeroutput>
5555
</screen>
@@ -176,15 +176,24 @@
176176

177177
<sect2>
178178
<title>Date and time differences</title>
179-
179+
180+
<para>
181+
Some of the queries in the <quote>timestamp</quote> test will
182+
fail if you run the test on the day of a daylight-savings time
183+
changeover, or the day before or after one. These queries assume
184+
that the intervals between midnight yesterday, midnight today and
185+
midnight tomorrow are exactly twenty-four hours -- which is wrong
186+
if daylight-savings time went into or out of effect meanwhile.
187+
</para>
188+
180189
<para>
181190
Most of the date and time results are dependent on the time zone
182191
environment. The reference files are generated for time zone
183192
PST8PDT (Berkeley, California) and there will be apparent
184193
failures if the tests are not run with that time zone setting.
185194
The regression test driver sets environment variable
186-
<envar>PGTZ</envar> to <literal>PST8PDT</literal> to ensure
187-
proper results. However, your system must provide library
195+
<envar>PGTZ</envar> to <literal>PST8PDT</literal>, which normally
196+
ensures proper results. However, your system must provide library
188197
support for the PST8PDT time zone, or the time zone-dependent
189198
tests will fail. To verify that your machine does have this
190199
support, type the following:
@@ -214,15 +223,6 @@ PGTZ='PST8PDT7,M04.01.0,M10.05.03'; export PGTZ
214223
pre-1970 PDT times to be displayed in PST instead. This will
215224
result in localized differences in the test results.
216225
</para>
217-
218-
<para>
219-
Some of the queries in the <quote>timestamp</quote> test will
220-
fail if you run the test on the day of a daylight-savings time
221-
changeover, or the day before or after one. These queries assume
222-
that the intervals between midnight yesterday, midnight today and
223-
midnight tomorrow are exactly twenty-four hours -- which is wrong
224-
if daylight-savings time went into or out of effect meanwhile.
225-
</para>
226226
</sect2>
227227

228228
<sect2>
@@ -363,24 +363,17 @@ testname/platformpattern=comparisonfilename
363363
</para>
364364

365365
<para>
366-
For example: the int2 regression test includes a deliberate entry
367-
of a value that is too large to fit in int2. The specific error
368-
message that is produced is platform-dependent; our reference
369-
platform emits
370-
<screen>
371-
<computeroutput>ERROR: pg_atoi: error reading "100000": Numerical result out of range</computeroutput>
372-
</screen>
373-
but a fair number of other Unix platforms emit
374-
<screen>
375-
<computeroutput>ERROR: pg_atoi: error reading "100000": Result too large</computeroutput>
376-
</screen>
366+
For example: some systems using older time zone libraries fail to apply
367+
daylight-savings corrections to dates before 1970, causing
368+
pre-1970 PDT times to be displayed in PST instead. This causes a
369+
few differences in the <filename>horology</> regression test.
377370
Therefore, we provide a variant comparison file,
378-
<filename>int2-too-large.out</filename>, that includes this
379-
spelling of the error message. To silence the bogus
371+
<filename>horology-no-DST-before-1970.out</filename>, which includes
372+
the results to be expected on these systems. To silence the bogus
380373
<quote>failure</quote> message on HPPA platforms, resultmap
381374
includes
382375
<programlisting>
383-
int2/hppa=int2-too-large
376+
horology/hppa=horology-no-DST-before-1970
384377
</programlisting>
385378
which will trigger on any machine for which config.guess's output
386379
begins with <quote><literal>hppa</literal></quote>. Other lines

0 commit comments

Comments
 (0)