[BUGS] BUG #3300: priority index on planner (feature request)

2007-05-23 Thread Fernando Romo
The following bug has been logged online: Bug reference: 3300 Logged by: Fernando Romo Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.4 Operating system: CentOS 4.4/5 Description:priority index on planner (feature request) Details: Dear Postgresql Team: I

[BUGS] priority index on planner (feature request)

2007-05-23 Thread Fernando Romo
Dear Postgresql Team: I have some strange behavior on simple queries (i don't know if is a bug, but i prefer to make a feature request), buy we need to tell to the planner a different index priority. For example, i have a table called "calls" with 11 million records, and i need to take the min() a

Re: [BUGS] ERROR: invalid input syntax for integer: ""

2007-05-23 Thread Tom Lane
Magnus Hagander <[EMAIL PROTECTED]> writes: > IIRC, the behavior of MSSQL will depend on the query plan. If it's a > plan that requires doesn't require materialization at all, it won't > figure it out until you get there. ... which is pretty much what we do, too. regards,

Re: [BUGS] ERROR: invalid input syntax for integer: ""

2007-05-23 Thread Magnus Hagander
Pit M. wrote: > >> It would have failed if you had run the cursor far enough to fetch one >> of the bad rows. >> >> regards, tom lane >> > The difference is that in one case the query fails and in the other the > FETCH command fails. > > > Our problem is that if a query succeeds we u

Re: [BUGS] ERROR: invalid input syntax for integer: ""

2007-05-23 Thread Pit M.
It would have failed if you had run the cursor far enough to fetch one of the bad rows. regards, tom lane The difference is that in one case the query fails and in the other the FETCH command fails. Our problem is that if a query succeeds we use a count(*) of that q

Re: [BUGS] [ADMIN]

2007-05-23 Thread Joshua Kramer
I already found that it's possible to store passwords in the file pgpass.conf in the %APPDATA% directory. But that file isn't stored in that location. In fact it doesn't exist in my disk. I already checked the "Store password" Filipe, You need to create that file yourself. Using the format

Re: [BUGS] ERROR: invalid input syntax for integer: ""

2007-05-23 Thread Tom Lane
"Pit M." <[EMAIL PROTECTED]> writes: > Following query fails in pgAdmin which is OK because the field PLZZ > contains characters: > select * from "PERSONEN" where (CAST("PERSONEN"."PLZZ" AS INTEGER) >= > 7 ); > but if using the same query with a cursor ist works: > START TRANSACTION; > DE

[BUGS] ERROR: invalid input syntax for integer: ""

2007-05-23 Thread Pit M.
Following query fails in pgAdmin which is OK because the field PLZZ contains characters: select * from "PERSONEN" where (CAST("PERSONEN"."PLZZ" AS INTEGER) >= 7 ); but if using the same query with a cursor ist works: START TRANSACTION; DECLARE c21112234 SCROLL CURSOR FOR select * from "

[BUGS] BUG #3299: pgadmin3 explain partial object name displayed

2007-05-23 Thread Ferdinand
The following bug has been logged online: Bug reference: 3299 Logged by: Ferdinand Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.4 Operating system: OpenSuSE 10.2 Description:pgadmin3 explain partial object name displayed Details: Hi! Pgadmin3 1.6.3 on Su