Greetings,
Please don't top-post on these lists.
* SATYANARAYANA NARLAPURAM (satyanarlapu...@gmail.com) wrote:
> Increasing checkpoint_timeout helps reduce the amount of log written to the
> disk. This has several benefits like, reduced number of WAL IO, archival
> load on the system, less networ
Increasing checkpoint_timeout helps reduce the amount of log written to the
disk. This has several benefits like, reduced number of WAL IO, archival
load on the system, less network traffic to the standby replicas. However,
this increases the crash recovery time and impact server availability.
Inve
> On 08/03/2020 8:26 AM Robert Haas wrote:
...
> I think this is what's called a double-write buffer, or what was tried
> some years ago under that name. A significant problem is that you
> have to fsync() the double-write buffer before you can write the WAL.
I don't think it does need to be f
On Mon, Aug 3, 2020 at 5:26 AM Daniel Wood wrote:
> If we can't eliminate FPW's can we at least solve the impact of it? Instead
> of writing the before images of pages inline into the WAL, which increases
> the COMMIT latency, write these same images to a separate physical log file.
> The key
I thought that the biggest reason for the pgbench RW slowdown during a
checkpoint was the flood of dirty page writes increasing the COMMIT latency.
It turns out that the documentation which states that FPW's start "after a
checkpoint" really means after a CKPT starts. And this is the really ca
