From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | y(dot)kikuchi0714(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17269: Why is virtual memory usage of PostgreSQL growing constantly? |
Date: | 2021-11-05 08:17:36 |
Message-ID: | 20211105.171736.1501334681512881760.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
At Wed, 03 Nov 2021 11:11:24 +0000, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote in
> 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?
Could you show us some settings? Maybe max_connections and work_mem
could be the starter.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2021-11-05 09:03:47 | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |
Previous Message | Kyotaro Horiguchi | 2021-11-05 06:07:08 | Re: BUG #17266: could not truncate file "base/126370/130666" to 0 blocks: Permission denied |