From: | Joao Junior <jcoj2006(at)gmail(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | shared buffers and startup process |
Date: | 2020-01-14 15:29:51 |
Message-ID: | CABnPa_iu8LB=g-Cau8BhvJ1M4rOKRxZK-qzKdzvoG=1=2rbZbQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
I have a master slave setup with streaming replication.
I have a lots of wal files that were moved from master but not applied yet
, a big delay in the replica.
The replica is not working on hotstandby mode , no conflicts to delay
wals apply on it.
I would like to know if increasing the amount of shared-buffers could help
the startup process applying the wals. I would like to know if in
the process of reading the wals and applying them, blocks that should be
written will be brought to shared buffer or not?? If yes, having a bigger
shared buffer will keep as much as possible the amount of pages there and
increase the startup process's speed avoiding pages's replacement and going
to the OS cache and maybe to the disk .
Does it make sense?
Thanks in advanced.
Regards,
Joao
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2020-01-15 02:48:00 | Re: shared buffers and startup process |
Previous Message | Thomas Kellerer | 2020-01-14 08:01:30 | Re: Bad query plan when you add many OR conditions |