"Dag Lem" writes:
> The effect of this (pretty serious) bug is that I am able to insert a value
> into an integer column and consistently get an entirely different value read
> out later.
> Unfortunately this happens on a large data set (3.6M rows), and I am not
> able to either reproduce with a
"brad" writes:
> Steps to recreate are below. The real value is improperly rounded when
> inserted into a field that is double. 94.31 is stored as 94.3099975585938
> when it is inserted into a double precision column.
This is not a bug, it's just the typical behavior of float arithmetic.
"94.31
On 02/11/2011 06:38 AM, Mauricio Agustin Roubineau wrote:
The following bug has been logged online:
Bug reference: 5879
Logged by: Mauricio Agustin Roubineau
Email address: mroubin...@hotmail.com
PostgreSQL version: 8.4
Operating system: Windows XP
Description:Postg
The following bug has been logged online:
Bug reference: 5880
Logged by: brad
Email address: smit...@gmail.com
PostgreSQL version: 8.4.5
Operating system: linux x64
Description:Rounding error when copying a REAL numeric value to
DOUBLE PRECISION
Details:
Steps to re
The following bug has been logged online:
Bug reference: 5879
Logged by: Mauricio Agustin Roubineau
Email address: mroubin...@hotmail.com
PostgreSQL version: 8.4
Operating system: Windows XP
Description:PostgreSQL can not load my data folder
Details:
PostgreSQL can
The following bug has been logged online:
Bug reference: 5876
Logged by: Dag Lem
Email address: d...@nimrod.no
PostgreSQL version: 9.0.3
Operating system: CentOS release 5.5, i686
Description:Incorrectly reported column value
Details:
The effect of this (pretty seri
"Savita" wrote:
> When I ran query to get the ids which ends with B1
> select id from table where id like '%B1'
> does not return me any rows. Should it be not returning row with
> id AB1? Is there known issue?
Oh, I did have one more thought after I posted -- what is the data
type of the id c
On Thu, Feb 10, 2011 at 11:02:40AM +, Savita wrote:
> When I ran query to get the ids which ends with B1
> select id from table where id like '%B1'
> does not return me any rows. Should it be not returning row with id AB1? Is
> there known issue?
is this by any chance char(x) datatype?
if yes
"Savita" wrote:
> PostgreSQL version: 8.3.5
> I have a table with id as primary key.
> When I ran query to get the ids which ends with B1
> select id from table where id like '%B1'
> does not return me any rows.
You might want to check all the bug fixes listed in the 8.3 bug fix
releases s
The following bug has been logged online:
Bug reference: 5878
Logged by: Jan-Peter Seifert
Email address: jan-peter.seif...@gmx.de
PostgreSQL version: 8.4.7
Operating system: Ubuntu 10.04 LTS
Description:BTREE_BUILD_STATS causes 'make check' to fail
Details:
Hello,
The following bug has been logged online:
Bug reference: 5877
Logged by: Savita
Email address: savita.ha...@gmail.com
PostgreSQL version: 8.3.5
Operating system: Solaris
Description:problem with wild char used in where clause
Details:
I have a table with id as prima
Hi,
Sorry, I unfortunately had the wrong window focused when hitting enter...
On Thursday, February 10, 2011 10:47:42 AM Andres Freund wrote:
> Timing is on.
> Pager is always used.
> psql (9.1devel, server 9.0.3)
> WARNING: psql version 9.1, server version 9.0.
> Some psql features migh
Hi,
Timing is on.
Pager is always used.
psql (9.1devel, server 9.0.3)
WARNING: psql version 9.1, server version 9.0.
Some psql features might not work.
Type "help" for help.
# \d category
column number 2 is out of range 0..1
results in:
Program received signal SIGSEGV, Segmentation f
13 matches
Mail list logo
