Re: Caching of Queries
От | Matt Clark |
---|---|
Тема | Re: Caching of Queries |
Дата | |
Msg-id | 012501c4aaf0$f12d0930$8300a8c0@solent обсуждение исходный текст |
Ответ на | Re: Caching of Queries (Tatsuo Ishii <t-ishii@sra.co.jp>) |
Ответы |
Re: Caching of Queries
|
Список | pgsql-performance |
> I don't know what you are exactly referring to in above URL > when you are talking about "potential pitfalls of pooling". > Please explain more. Sorry, I wasn't implying that pgpool doesn't deal with the issues, just that some people aren't necessarily aware of them up front. For instance, pgpool does an 'abort transaction' and a 'reset all' in lieu of a full reconnect (of course, since a full reconnect is exactly what we are trying to avoid). Is this is enough to guarantee that a given pooled connection behaves exactly as a non-pooled connection would from a client perspective? For instance, temporary tables are usually dropped at the end of a session, so a client (badly coded perhaps) that does not already use persistent connections might be confused when the sequence 'connect, create temp table foo ..., disconnect, connect, create temp table foo ...' results in the error 'Relation 'foo' already exists'.
В списке pgsql-performance по дате отправления: