From: | Mohammed Afsar <mohammed(dot)afsar7799(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Postgresql background writer and checkpointer memory utilization in Linux server |
Date: | 2020-08-11 15:46:27 |
Message-ID: | CA+s2FCP4CtJ2rHFR890gt7v9g5anLwm6W8fxFbBMb5LMpOsrOQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Dear Tom,
This issue is occurred in postgresql 11 version only not in postgresql 9.4
and also in postgresql Linux environments I have seen when there is no
transaction running database background processes are not going to occupies
the server memory.
Regards,
Mohammed Afsar
On Tue, Aug 11, 2020, 9:10 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Mohammed Afsar <mohammed(dot)afsar7799(at)gmail(dot)com> writes:
> > Thanks for response,the exact issue which am facing is when there is no
> > transaction queries are happening in database checkpointer and background
> > writer is continuously utilizing memory from server.
>
> That sounds like complete nonsense. Those processes don't execute
> queries. It's true that they'll continue to do I/O work for some
> time after queries have executed in other processes, but that's normal.
>
> I say again that you haven't offered any evidence of having a problem
> to solve. If you don't want the database to be consuming any cycles
> at all, then you should shut it down. But if you want it to do useful
> work, it's designed to spread out that work, not necessarily to do it
> all before a query returns results to the client.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Stephane Simard | 2020-08-11 20:44:44 | Restore DB into Azure |
Previous Message | Tom Lane | 2020-08-11 15:40:21 | Re: Postgresql background writer and checkpointer memory utilization in Linux server |