| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Alexander Pyhalov <alp(at)sfedu(dot)ru>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL memory usage |
| Date: | 2019-10-17 11:09:14 |
| Message-ID: | 9d662d4588db8f77f8bb2c9bab360f77021aadc5.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alexander Pyhalov wrote:
> After looking at my DBMS server for some time I've understood that I don't understand what was going on...
>
> A server has 48 GB RAM. shared_buffers is set to 12GB, work_mem - to 32MB, pgbouncer
> in transaction mode is used to connect pool (pool size 80) to PostgreSQL 10.5 server.
>
> I see that at some point several postgresql backends start consuming about 16 GB RAM.
> If we account for shared_buffers, it meens 4 GB RAM for private backend memory.
> How can we achieve such numbers? I don't see any long-running (or complex) queries
> (however, there could be long-running transactions and queries to large partitioned tables).
> But how could they consume 512* work_mem memory?
A wild guess: you are using large data items, or you have PostGIS installed,
which is known to use lots of memory for certain operations, which is not
limited by "work_mem".
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M Tarkeshwar Rao | 2019-10-17 11:16:29 | Can you please tell us how set this prefetch attribute in following lines. |
| Previous Message | Tom Lane | 2019-10-17 10:24:10 | Re: v12 and pg_restore -f- |