Re(2): 7.0.3 BUG

From: "pgsql-sql" <pgsql-sql(at)fc(dot)emc(dot)com(dot)ph>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re(2): 7.0.3 BUG
Date: 2000-11-25 07:22:15
Message-ID: fc.000f567200818c73000f567200818c73.818c7f@fc.emc.com.ph
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

tgl(at)sss(dot)pgh(dot)pa(dot)us writes:
>"pgsql-sql" <pgsql-sql(at)fc(dot)emc(dot)com(dot)ph> writes:
>> migrate=# select userid from users where userid = 'reynan(at)yahoo(dot)com';
>> userid
>> ---------------------
>> reynan(at)yahoo(dot)com
>> admin
>> (2 rows)
>
>That's a tad, um, startling :-(
>
>However, you haven't given us nearly enough information to have a shot
>at figuring out what's going on.
>
> regards, tom lane

The query used indexscan. I tried using trim in userid and I got something
like ...
migrate=# select userid from users where trim(userid) = 'reynan(at)yahoo(dot)com';
userid
---------------------
reynan(at)yahoo(dot)com
(1 row)

I thought it was a varchar problem ('coz userid is varchar) of 7.0.3 so I
changed to 7.0.2.
Is it really a varchar bug?
Anyway, I dumped all the database. When I was restoring it in 7.0.2 I got
these ...

You are now connected as new user root.
CREATE
You are now connected as new user pgsql.
ERROR: copy: line 3910, Bad timestamp external representation '2000-01-05
00:00:60.00+08'
PQendcopy: resetting connection
ERROR: copy: line 3910, Bad timestamp external representation '2000-01-05
00:00:60.00+08'
PQendcopy: resetting connection
ERROR: copy: line 302, Bad timestamp external representation '2000-02-29
00:00:60.00+08'
PQendcopy: resetting connection
ERROR: copy: line 13, Bad timestamp external representation '1970-01-01
08:04:60.00+08'
PQendcopy: resetting connection
ERROR: copy: line 24, Bad timestamp external representation '1970-01-01
08:04:60.00+08'
PQendcopy: resetting connection
You are now connected as new user root.
ERROR: copy: line 2, Bad timestamp external representation '1999-12-24
00:00:60.00+08'
PQendcopy: resetting connection
You are now connected as new user pgsql.
CREATE

I took a look at the database named 'migrate' (this is where the error
occured),
the tables were all empty. Most of the tables have field like this...

createdate | timestamp | not null default now()

Weird because those timestamps were generated by default now(). Is this an
another bug (timestamp bug)?
Take a look at this ...

migrate=# select version();
version
---------------------------------------------------------------
PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc 2.95.3
(1 row)

migrate=# select '2000-01-05 00:00:60.00+08'::timestamp;
ERROR: Bad timestamp external representation '2000-01-05 00:00:60.00+08'
migrate=# select '2000-11-25 14:05:23.00+08'::timestamp;
?column?
---------------------------
2000-11-25 14:05:23.00+08
(1 row)

migrate=# create table testing (datetime timestamp);
CREATE
migrate=# insert into testing values('2000-01-05 00:00:60.00+08');
ERROR: Bad timestamp external representation '2000-01-05 00:00:60.00+08'
migrate=# insert into testing values('2000-11-25 14:05:23.00+08');
INSERT 6834235 1
migrate=#

Thanks,
sherwin

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2000-11-25 16:28:58 Re: Re(2): 7.0.3 BUG
Previous Message Ramesh H R 2000-11-25 07:20:28 How to set autocommit true/false from a java program