[BUGS] Postgres throwing exception for int8 datatype.

I am running postgres 7.1 version on a Mips platform running Linux (2.4.17sb20020611 version). The postgres source is compiled with Montevista cross compiler (gcc version 3.0.1) for the mips platform. Postgres is throwing following exception when a record is inserted with int8 datatype. Note

[BUGS] help

Hi, i am new to linux. so I want to install postgress in windows. please please tell me the steps/ procedure to install postgress in windows 2000. i have downloaded cygwin, tcl84b1.. in search of an way to install postgress in windows. I work mostly on php / mysql and theres no prob with worki

[BUGS] PG 7.1: VIEW returns fewer rows than equivalent select

Hi, I created a view with this SQL: create view category_type as select l1.id as cat_id, l1.description as cat_desc,l2.id as cat_typ_id, l2.description as cat_type_desc,p.id as link_id from levels l1 join product_category p on p.category = l1.id and p.category

Re: [BUGS] pg_ctl failure with older Bourne shells (use ${1:+"$@"})

Blah. Yeah, I muffed that--don't use a colon. Regarding Bruce's comment, you wouldn't think they're still around, but this is what /bin/sh does on Tru64 5.1. (5.1 is almost the latest version; there's a 5.1a.) Mike > -Original Message- > From: Tom Lane [mailto:[EMAIL PROTECTED]] > S

Re: [BUGS] PG 7.1: VIEW returns fewer rows than equivalent select

Bradley Kieser <[EMAIL PROTECTED]> writes: > When I run it, it returns 36 rows. > Now, if I cut and paste simply the SELECT part and run it, I get the > correct number of rows, 170. If you can reproduce this on something more recent than 7.1, I'd appreciate seeing a complete (self-contained) ex

[BUGS] pg_ctl -w option does not behave as documented

PostgreSQL 7.2.1 / SUSE Linux 8.0   According to the output of "pg_ctl --help", the -w option (lowercase) should force the frontend to wait until the postmaster's startup completes. Instead it prompts for a password, as with the (-W) option (uppercase). Ommiting the option, the frontend stil

Re: [BUGS] Bug #672: timestamp() converts timezone in wrong direction

I didn't see any follow-up to this bug. The problem is that the "datetime"/"timestamp" functions do not calculate the date from the seconds since the unix epoch correctly. In bug #695, Tom Lane states that the "timestamp" type is moving in the direction of timestamp without timezone. It appear

Re: [BUGS] Postgres throwing exception for int8 datatype.

"Niranjan Shivaratri" <[EMAIL PROTECTED]> writes: > I am running postgres 7.1 version on a Mips platform running Linux (2.4.17sb20020611 >version). > The postgres source is compiled with Montevista cross compiler (gcc version 3.0.1) >for the mips platform. In a cross-compilation setup you'll p

[BUGS] VACUUM FULL changes the order of rows in a table?

WARNING: Not sure if what I am about to describe is a bug. The PostgreSQL 7.2.1 Documentation for VACUUM says: "VACUUM FULL does more extensive processing, including moving of tuples across blocks to try to compact the table to the minimum number of disk blocks." Does above quote expla