CVS tip problems

From: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>
To: pgsql-hackers(at)postgresql(dot)org
Subject: CVS tip problems
Date: 2004-05-30 21:53:12
Message-ID: 1085953992.26732.1339.camel@linda
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

CVS tip built on Debian unstable, i386, Linux 2.6.5 SMP.
gcc 3.3.3

./configure --with-openssl --with-pam --with-krb5 --with-gnu-ld
--with-python --with-perl --with-tcl --with-pgport=5342
--enable-thread-safety --enable-nls --enable-integer-datetimes
--enable-debug --enable-cassert --enable-depend

1. There are regression failures on timestamptz and horology which seem
to have come about either on input or output of timestamps with
fractional seconds. I tried various inputs and found that certain
timestamps with fractional seconds had one second added to the time.
This appears to be confined to the period from midnight at the start of
Dec 14 1901 GMT to midnight at the start of Jan 01 2000 GMT

junk=# select cast('Dec 13 15:59:59.50 1901 PST' as timestamptz);
timestamptz
------------------------
1901-12-13 23:59:59.50
(1 row)

junk=# select cast('Dec 13 16:00:59.50 1901 PST' as timestamptz);
timestamptz
---------------------------
1901-12-14 00:01:00.50+00
(1 row)

junk=# select cast('Dec 13 23:59:59.50 1901 GMT' as timestamptz);
timestamptz
------------------------
1901-12-13 23:59:59.50
(1 row)

junk=# select cast('Dec 14 00:00:00.50 1901 GMT' as timestamptz);
timestamptz
---------------------------
1901-12-14 00:00:01.50+00
(1 row)

I tried debugging this but got a segmentation fault and apparent stack
corruption in gdb, with the reported break point not anywhere I had set
one. I don't know what to do about that.

2. If the postmaster is not running, there is garbage in psql's error
message:

olly(at)linda$ export PGPORT=5342
olly(at)linda$ export PATH=/usr/local/pgsql/bin:$PATH
olly(at)linda$ psql junk
psql: could not connect to server: ,*(at)È %(at)
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5342"?

olly(at)linda$ psql -h localhost junk
psql: could not connect to server: ,*(at)È %(at)
Is the server running on host "localhost" and accepting
TCP/IP connections on port 5342?

3. There is a compilation warning that a constant will not fit into a
long in adt.c. There are two more files where INT64CONST() is required
but not supplied. Patch attached.

--
Oliver Elphick olly(at)lfix(dot)co(dot)uk
Isle of Wight http://www.lfix.co.uk/oliver
GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA
========================================
"Do all things without murmurings and disputings;
that ye may be blameless and harmless, the sons of
God, without rebuke, in the midst of a crooked and
perverse nation, among whom ye shine as lights in the
world." Philippians 2:14,15

Attachment Content-Type Size
date64.patch text/x-patch 3.0 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Jowett 2004-05-30 22:23:47 Re: v3 protocol & string encoding
Previous Message Darko Prenosil 2004-05-30 20:44:14 Re: yet another contrib module

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-05-31 06:31:14 Re: CVS tip problems
Previous Message Tom Lane 2004-05-30 21:31:55 Re: use new List API names