BUG #1753: Query Optimizer does not work well with libpg / PQexecParams
| От | Ernst Bachmann |
|---|---|
| Тема | BUG #1753: Query Optimizer does not work well with libpg / PQexecParams |
| Дата | |
| Msg-id | 20050705090906.3DC5CF0B0E@svr2.postgresql.org обсуждение |
| Ответы |
Re: BUG #1753: Query Optimizer does not work well with libpg
|
| Список | pgsql-bugs |
The following bug has been logged online: Bug reference: 1753 Logged by: Ernst Bachmann Email address: e.bachmann@xebec.de PostgreSQL version: 8.0.3 Operating system: Linux Description: Query Optimizer does not work well with libpg / PQexecParams Details: It looks like the query optimizer isn't taking the value of parameters sent with PQexecParams into account, thus generating (in my case, very) unoptimal plans There is a warning about that for "PREPARE", but with PQexecParams, the parameter values should be available immediatly for the planner. Sending the parameters inline in the SQL query string solved the problem for me (Query executes in 5 ms instead of 500+), but thats obviously not my favorite solution. Is this something planned to be fixed, otherwise a warning in the libpq documentation about "PQexecParams" being potentially slow would be nice. Thanks /Ernst
В списке pgsql-bugs по дате отправления: