From: | 菊池祐 <y(dot)kikuchi0714(at)gmail(dot)com> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | 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 09:15:01 |
Message-ID: | CAGS+-sSqx9C3+WDJPMNCoV2rddP1h-JoxoFYY1+aFyVEPBWLpQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thank you for replying.
I attached postgresql.conf file.
2021年11月5日(金) 17:17 Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>:
> 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
>
Attachment | Content-Type | Size |
---|---|---|
postgresql.conf | application/octet-stream | 23.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2021-11-05 10:01:26 | BUG #17272: Incorrect syntax parsed |
Previous Message | Noah Misch | 2021-11-05 09:03:47 | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |