Re: [SQL] 7.0.3 BUG

2000-11-30 Thread Thomas Lockhart
> >> ERROR: copy: line 3910, Bad timestamp external representation > >> '2000-01-05 00:00:60.00+08' > >> Weird because those timestamps were generated by default now(). ... > Is there a work-around to this aside from manually changing the dump file? > Distribution Version: Linux Mandrake

Re(2): [SQL] 7.0.3 BUG

2000-11-28 Thread pgsql-sql
Thanks to you Tom and Thomas. Now I know. - sherwin [EMAIL PROTECTED] writes: >Ah ha (or rather, ha ha ha)! I'd suggest using the RPMs posted on the >postgresql.org ftp site, which include a sample .rpmrc file which fixes >disasterous bugs in Mandrake's default compiler settings for building >RP

Re: Re(2): Re(2): [SQL] 7.0.3 BUG

2000-11-27 Thread Alain Toussaint
> >That's a rather interesting version report, seeing as how there is > >no such gcc release as 2.95.3 according to the GCC project's homepage. quick tidbit,there's no gcc 2.95.3 from GCC's but there's is one from Pentium gcc (see ),the pentium gcc group in this case used g

Re(2): Re(2): [SQL] 7.0.3 BUG

2000-11-26 Thread pgsql-sql
[EMAIL PROTECTED] writes: >"pgsql-sql" <[EMAIL PROTECTED]> writes: >> ERROR: copy: line 3910, Bad timestamp external representation >'2000-01-05 >> 00:00:60.00+08' > >> Weird because those timestamps were generated by default now(). > >Weird, all right. I can get 7.0.2 to emit an incorrect repre

Re: Re(2): [SQL] 7.0.3 BUG

2000-11-25 Thread Tom Lane
"pgsql-sql" <[EMAIL PROTECTED]> writes: > ERROR: copy: line 3910, Bad timestamp external representation '2000-01-05 > 00:00:60.00+08' > Weird because those timestamps were generated by default now(). Weird, all right. I can get 7.0.2 to emit an incorrect representation like that by constructin

Re(2): [SQL] 7.0.3 BUG

2000-11-24 Thread pgsql-sql
[EMAIL PROTECTED] writes: >"pgsql-sql" <[EMAIL PROTECTED]> writes: >> migrate=# select userid from users where userid = '[EMAIL PROTECTED]'; >>userid >> - >> [EMAIL PROTECTED] >> admin >> (2 rows) > >That's a tad, um, startling :-( > >However, you haven't given us nea

Re: [SQL] 7.0.3 BUG

2000-11-24 Thread Tom Lane
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > Just a wild guess, but I would imagine > a corrupt (old) index on the userid field would > cause this kind of behavior. A corrupt index might be a contributing factor, but it doesn't seem like it could be the only one. From what I know of the in

Re: [SQL] 7.0.3 BUG

2000-11-24 Thread [EMAIL PROTECTED]
Just a wild guess, but I would imagine a corrupt (old) index on the userid field would cause this kind of behavior. You could test this by dropping the index and then rebuilding it. Troy > > "pgsql-sql" <[EMAIL PROTECTED]> writes: > > migrate=# select userid from users where userid = '[EMAI

Re: [SQL] 7.0.3 BUG

2000-11-24 Thread Tom Lane
"pgsql-sql" <[EMAIL PROTECTED]> writes: > migrate=# select userid from users where userid = '[EMAIL PROTECTED]'; >userid > - > [EMAIL PROTECTED] > admin > (2 rows) That's a tad, um, startling :-( However, you haven't given us nearly enough information to have a shot

[SQL] 7.0.3 BUG

2000-11-24 Thread pgsql-sql
SELECT is returning bogus data. migrate=# select version(); version --- PostgreSQL 7.0.3 on i686-pc-linux-gnu, compiled by gcc 2.95.3 (1 row) migrate=# select userid from users where userid = '[EMAIL PROTECT