| From: | Don Seiler <don(at)seiler(dot)us> |
|---|---|
| To: | Sushil Shirodkar <sushilps(at)hotmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: vacuumdb causes memory drain. |
| Date: | 2018-04-26 15:33:27 |
| Message-ID: | CAHJZqBCr0Xyp_58iXpknrTrXQFoYc3BPCqY8G0h-STzaMWLsqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
>
How are you measuring free memory? Memory might be listed in cached/buffers
instead of free but is still available. Although that wouldn't then explain
other processes being slow.
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sushil Shirodkar | 2018-04-26 15:47:25 | Re: vacuumdb causes memory drain. |
| Previous Message | Sushil Shirodkar | 2018-04-26 15:31:01 | vacuumdb causes memory drain. |