Re: PREPARE / EXECUTE
От | Zeugswetter Andreas SB SD |
---|---|
Тема | Re: PREPARE / EXECUTE |
Дата | |
Msg-id | 46C15C39FEB2C44BA555E356FBCD6FA4961ED1@m0114.s-mxs.net обсуждение исходный текст |
Ответ на | PREPARE / EXECUTE (Hans-Jürgen Schönig <postgres@cybertec.at>) |
Ответы |
Re: PREPARE / EXECUTE
|
Список | pgsql-hackers |
> The idea is not to have it accross multiple backends and having it in > sync with the tables in the database. This is not the point. > My problem is that I have seen many performance critical applications > sending just a few complex queries to the server. The problem is: If you > have many queries where the relation "time planner"/"time executor" is > very high (eg. complex joins with just one value as the result). The standard approach to such a scenario would imho be to write stored procedures for the complex queries (e.g. plpgsql) and use that from the client. Maybe even eliminate a few ping pongs between client and server. Andreas
В списке pgsql-hackers по дате отправления: