[BUGS] BUG #7495: chosen wrong index

2012-08-15 Thread psql
The following bug has been logged on the website: Bug reference: 7495 Logged by: Andreas Email address: p...@elbrief.de PostgreSQL version: 9.1.4 Operating system: Debian Linux Description: Hello. create table bla ( a int , b int ) ; insert into bla ( a , b ) select

Re-2: [BUGS] BUG #7495: chosen wrong index

2012-08-16 Thread psql
on between a and b. By my data psql must scan mostly all data to find the rows. This is only an example. In my live environment i have a table with a boolean where the boolean is usually true. The boolean is false on new or changed entrys and if i select the false-rows order by primary key i get slo

Re-2: [BUGS] BUG #7495: chosen wrong index

2012-08-16 Thread psql
on between a and b. By my data psql must scan mostly all data to find the rows. This is only an example. In my live environment i have a table with a boolean where the boolean is usually true. The boolean is false on new or changed entrys and if i select the false-rows order by primary key i get slo

Re-2: [BUGS] BUG #7495: chosen wrong index

2012-08-16 Thread psql
on between a and b. By my data psql must scan mostly all data to find the rows. This is only an example. In my live environment i have a table with a boolean where the boolean is usually true. The boolean is false on new or changed entrys and if i select the false-rows order by primary key i get slo

Re-2: [BUGS] BUG #7495: chosen wrong index

2012-08-16 Thread psql
on between a and b. By my data psql must scan mostly all data to find the rows. This is only an example. In my live environment i have a table with a boolean where the boolean is usually true. The boolean is false on new or changed entrys and if i select the false-rows order by primary key i get slo

Re-2: [BUGS] BUG #7495: chosen wrong index

2012-08-16 Thread psql
on between a and b. By my data psql must scan mostly all data to find the rows. This is only an example. In my live environment i have a table with a boolean where the boolean is usually true. The boolean is false on new or changed entrys and if i select the false-rows order by primary key i get slo

[BUGS] BUG #8214: SIGSEGV in PyEval_EvalFrameEx

2013-06-05 Thread m+psql
The following bug has been logged on the website: Bug reference: 8214 Logged by: Miron Cuperman Email address: m+p...@tradehill.com PostgreSQL version: 9.2.4 Operating system: Debian 6.0 (squeeze) Description: This is an intermittent crash during a ~5 minute unit test

[BUGS] BUG #6021: There is no difference between default and empty access privileges with \dp

2011-05-11 Thread psql dp showing empty Access privileges column for {}
The following bug has been logged online: Bug reference: 6021 Logged by: psql \dp showing empty Access privileges column for {} Email address: gszpetkow...@gmail.com PostgreSQL version: 9.0.4 Operating system: Debian Squeeze Description:There is no difference between

[BUGS] BUG #4927: psql does "spoil" the query before sending it to server

2009-07-17 Thread handling numeric literals with dots in psql copy command
The following bug has been logged online: Bug reference: 4927 Logged by: handling numeric literals with dots in psql \copy command Email address: filip.rembialkow...@gmail.com PostgreSQL version: 8.4.0 Operating system: Linux Description:psql does "spoil"