Hi!
I would like to know how postgres will behave with a big amount of cached
plans from prepared statements on 1 connection. Let's say there is an
application level connection pooling and one connection can last for many
weeks. Many plans are cached from many prepared statements, is there any
postgres management of that or it is totally system thing? 
Some plans will be evicted from process memory at some point of time or they
will be kept infinitely causing huge amount of memory being allocated for
this connection?



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html

Reply via email to