| From: | Alexander Pyhalov <alp(at)sfedu(dot)ru> |
|---|---|
| To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | PostgreSQL memory usage |
| Date: | 2019-10-16 16:29:55 |
| Message-ID: | AM6PR05MB61985241B3104D09D7A992F6CF920@AM6PR05MB6198.eurprd05.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello.
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?
С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2019-10-16 17:21:48 | Re: v12 and pg_restore -f- |
| Previous Message | Alan Hodgson | 2019-10-16 15:50:59 | Re: Text search lexer's handling of hyphens and negatives |