From af3487e9bf849c0e54b5a42bc093d3f5b726434c Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 6 Aug 2001 22:53:26 +0000 Subject: [PATCH] Update now-obsolete example of platform-specific regression comparison files. --- doc/src/sgml/regress.sgml | 49 ++++++++++++++++++++--------------------------- 1 file changed, 21 insertions(+), 28 deletions(-) diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml index 74ad9e71f9..96d421a7f6 100644 --- a/doc/src/sgml/regress.sgml +++ b/doc/src/sgml/regress.sgml @@ -1,4 +1,4 @@ - + Regression Tests @@ -49,7 +49,7 @@ ====================== - All 76 tests passed. + All 77 tests passed. ====================== @@ -176,15 +176,24 @@ Date and time differences - + + + Some of the queries in the timestamp test will + fail if you run the test on the day of a daylight-savings time + changeover, or the day before or after one. These queries assume + that the intervals between midnight yesterday, midnight today and + midnight tomorrow are exactly twenty-four hours -- which is wrong + if daylight-savings time went into or out of effect meanwhile. + + Most of the date and time results are dependent on the time zone environment. The reference files are generated for time zone PST8PDT (Berkeley, California) and there will be apparent failures if the tests are not run with that time zone setting. The regression test driver sets environment variable - PGTZ to PST8PDT to ensure - proper results. However, your system must provide library + PGTZ to PST8PDT, which normally + ensures proper results. However, your system must provide library support for the PST8PDT time zone, or the time zone-dependent tests will fail. To verify that your machine does have this support, type the following: @@ -214,15 +223,6 @@ PGTZ='PST8PDT7,M04.01.0,M10.05.03'; export PGTZ pre-1970 PDT times to be displayed in PST instead. This will result in localized differences in the test results. - - - Some of the queries in the timestamp test will - fail if you run the test on the day of a daylight-savings time - changeover, or the day before or after one. These queries assume - that the intervals between midnight yesterday, midnight today and - midnight tomorrow are exactly twenty-four hours -- which is wrong - if daylight-savings time went into or out of effect meanwhile. - @@ -363,24 +363,17 @@ testname/platformpattern=comparisonfilename - For example: the int2 regression test includes a deliberate entry - of a value that is too large to fit in int2. The specific error - message that is produced is platform-dependent; our reference - platform emits - -ERROR: pg_atoi: error reading "100000": Numerical result out of range - - but a fair number of other Unix platforms emit - -ERROR: pg_atoi: error reading "100000": Result too large - + For example: some systems using older time zone libraries fail to apply + daylight-savings corrections to dates before 1970, causing + pre-1970 PDT times to be displayed in PST instead. This causes a + few differences in the horology regression test. Therefore, we provide a variant comparison file, - int2-too-large.out, that includes this - spelling of the error message. To silence the bogus + horology-no-DST-before-1970.out, which includes + the results to be expected on these systems. To silence the bogus failure message on HPPA platforms, resultmap includes -int2/hppa=int2-too-large +horology/hppa=horology-no-DST-before-1970 which will trigger on any machine for which config.guess's output begins with hppa. Other lines -- 2.11.0