Re: Understanding the output of make check

Hi,

I've just compiled 9.1.1 in 32bit on Solaris snv_134 ("OpenSolaris
2010.11") with the Solaris Studio Compilers 12.2. The following Problem
is displayed

Maybe I'm blind, but where is the difference diff sees?

Thomas

*** /tmp/postgresql-9.1.1/src/test/regress/expected/timestamptz.out
Thu Sep 22 23:57:57 2011
--- /tmp/postgresql-9.1.1/src/test/regress/results/timestamptz.out
Sat Oct 22 14:34:41 2011
***************
*** 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

miesi <miesi(at)pc-h(dot)de> writes:
> Maybe I'm blind, but where is the difference diff sees?

PST vs PDT. Apparently you're using a system-provided timezone database
that lacks support for wider-than-32-bit time_t, so that dates beyond
2038 aren't handled correctly.

regards, tom lane