From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Sushil Shirodkar <sushilps(at)hotmail(dot)com> |
Cc: | "don(at)seiler(dot)us" <don(at)seiler(dot)us>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: vacuumdb causes memory drain. |
Date: | 2018-04-30 05:43:03 |
Message-ID: | 1525066983.2466.5.camel@cybertec.at |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Sushil Shirodkar wrote:
> > > > > > > On Thu, Apr 26, 2018 at 10:31 AM, Sushil Shirodkar <sushilps(at)hotmail(dot)com> wrote:
> > > > > > > Running "vacuumdb -a -z -v" from the cron on one of our test environment, and
> > > > > > > noticed that memory of the server goes down from 3.4GB free to 150MB. Once
> > > > > > > the process is over, memory is not released, is it normal or something needs to be
> > > > > > > changed ? also other processes start running slow afterwards due to low memory.
>
> Process which was running close to 99% memory was
> "/usr/lib/postgresql/9.5/bin/postgres -D /var/lib/postgresql/9.5/main -c config_file=/etc/postgresql/9.5/main/postgresql.conf"
>
> free -h - was showing between 100-150 mb free.
>
> shared_buffers = 1GB
> maintenance_work_mem = 256MB
Can you share the "free -h" output?
What do you get for
ps -p <postmaster PID> -o rss,trs,drs,vsz,%mem
if you substitute the postmaster's process ID?
If you say that "sync" restored normal behavior, are you implying that there
was a high I/O load?
Still trying to figure out what exactly you are experiencing.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Sushil Shirodkar | 2018-04-30 15:03:47 | Re: vacuumdb causes memory drain. |
Previous Message | Sushil Shirodkar | 2018-04-30 01:23:57 | Re: vacuumdb causes memory drain. |