Re: Partitioned checkpointing

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Takashi Horikawa <t-horikawa(at)aj(dot)jp(dot)nec(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Partitioned checkpointing
Date: 2015-09-10 10:33:08
Message-ID: alpine.DEB.2.10.1509101229350.30046@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I don't feel that another source of the performance dip has been heartily
> addressed; full-page-write rush, which I call here, would be a major issue.
> That is, the average size of transaction log (XLOG) records jumps up sharply
> immediately after the beginning of each checkpoint, resulting in the
> saturation of WAL write path including disk(s) for $PGDATA/pg_xlog and WAL
> buffers.

On this point, you may have a look at this item:

https://commitfest.postgresql.org/5/283/

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2015-09-10 10:59:41 Another typo in comment in setrefs.c
Previous Message Fabien COELHO 2015-09-10 09:59:58 Re: Partitioned checkpointing