Search Postgresql Archives

Re: Per-session memory footprint (9.0/windows)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hannes Erven <hannes@xxxxxxxx> writes:
> It is still about 5 MB of private memory per "idle" backend process. Is
> there anything I can do to optimize?

That sounds about the right ballpark for a working backend process with
caches loaded up.  If that's too much for you, you ought to be using
connection pooling.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux