Odd behaviour of timestamptz

From: Matteo Beccati <php(at)beccati(dot)com>
To: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Odd behaviour of timestamptz
Date: 2007-02-21 08:15:58
Message-ID: 45DBFFBE.2050403@beccati.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I've been recently pointed out an issue with timestamptz on a fedora box
and no one was able to replicate it on other machines. After a quick
chat on the IRC at least another two people could replicate the issue
and all of them were using an RPM package.

PostgreSQL 8.2.3 on i686-redhat-linux-gnu, compiled by GCC gcc (GCC)
3.4.6 20060404 (Red Hat 3.4.6-3)

test=# create TABLE test (data timestamp with time zone);
CREATE TABLE

test=# INSERT into test values ('1910-01-10');
INSERT 0 1

test=# INSERT into test values ('1990-01-10');
INSERT 0 1

test=# SELECT * from test;
data
----------------------------
1910-01-10 00:00:00+00:19:32
1990-01-10 00:00:00+01
(2 rows)

Similar issues were reported using 8.1.8 on RHEL3:

test=# SELECT * from test2;
data
---------------------------
1910-01-10 00:00:00+00:09
1990-01-10 00:00:00+01
(2 rows)

another 8.2.3 on FC3:

test=# SELECT * from test;
data
------------------------------
1910-01-10 00:00:00+00:09:21
1990-01-10 00:00:00+01
(2 lignes)

and another machine:

test=# SELECT * from test;
data
---------------------------
1910-01-10 00:00:00+01:24
1990-01-10 00:00:00+01
(2 rows)

Best regards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Glaesemann 2007-02-21 08:35:40 Re: Odd behaviour of timestamptz
Previous Message Stefan Kaltenbrunner 2007-02-21 06:58:02 Re: Out of memory on vacuum analyze