| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | y(dot)kikuchi0714(at)gmail(dot)com |
| Subject: | BUG #17269: Why is virtual memory usage of PostgreSQL growing constantly? |
| Date: | 2021-11-03 11:11:24 |
| Message-ID: | 17269-33419c48264f6532@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17269
Logged by: Yu Kikuchi
Email address: y(dot)kikuchi0714(at)gmail(dot)com
PostgreSQL version: 9.6.17
Operating system: Windows Server 2016
Description:
Hi, our team uses the PostgreSQL 9.6 database.
A few days ago, we changed memory size because the ratio of memory was about
70-80%.
Accordingly, we changed sharred_buffers in postgresql.conf.
Before
・memory:64GB
・shared_buffers:16GB
After
・memory:128GB
・shared_buffers:32GB
The radio of memory is about 20% after we changed memory size, but
PostgreSQL uses virtual memory constantly.
PostgreSQL finally ran out of virtual memory a few hours later.
Why did PostgreSQL use virtual memory although there is an available memory?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-11-03 11:48:12 | BUG #17270: Partitions are not prunned for generic plans when `ANY` construct is used. |
| Previous Message | Heikki Linnakangas | 2021-11-03 10:39:18 | Re: Snapshot leak warning with lo_export in subtransaction |