Merlin Moncure-2 wrote:
>
>
> ... I've coded a
> lot of multi schema designs and they tend to either go the one
> session/schema route or the connection pooling route. Either way,
> cache memory usage tends to work itself out pretty well (it's never
> been a problem for me before at least). I can't recall anyone ever
> even complaining about it in a non synthetic test.
>
>
It's good to know that. Many thanks to your help. :)
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/PostgreSQL-backend-process-high-memory-usage-issue-tp4289407p4301555.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
