[BUGS] Integer parsing bug?

2004-02-28 Thread Steve Atkins
Section 8.1 of the manual gives the range of an integer as -2147483648 to +2147483647. template1=# select '-2147483648'::int; int4 - -2147483648 (1 row) template1=# select -2147483648::int; ERROR: integer out of range Oops. template1=# select version();

Re: [BUGS] Integer parsing bug?

2004-03-03 Thread Steve Atkins
On Wed, Mar 03, 2004 at 12:31:47PM -0500, Bruce Momjian wrote: > Yep, it definately looks weird: > > test=> select '-2147483648'::int; > int4 > - >-2147483648 > (1 row) > > test=> select -2147483648::int; > ERROR: integer o

Re: [BUGS] Integer parsing bug?

2004-03-03 Thread Steve Atkins
On Wed, Mar 03, 2004 at 06:27:07PM -0500, Tom Lane wrote: > Steve Atkins <[EMAIL PROTECTED]> writes: > >> test=> select -2147483648::int; > >> ERROR: integer out of range > > There is no bug here. You are mistakenly assuming that the above > represents &

[BUGS] BUG #5589: psql dies with bad free() in libedit

2010-08-01 Thread Steve Atkins
The following bug has been logged online: Bug reference: 5589 Logged by: Steve Atkins Email address: st...@blighty.com PostgreSQL version: 9.0beta3 Operating system: OS X Description:psql dies with bad free() in libedit Details: I have a database that contains two

Re: [BUGS] BUG #5589: psql dies with bad free() in libedit

2010-08-01 Thread Steve Atkins
On Aug 1, 2010, at 10:11 PM, Tom Lane wrote: > "Steve Atkins" writes: >> I have a database that contains two tables (partminer and partminer2), and >> two sequences (partminer2_id_seq and partminer_pk), on a 9.0beta3 >> installation built from source with default