Re: Is there any impact if "#wal_keep_segments = 0 " and "checkpoint_segments = 128" postgresql.conf file.

From: "Jehan-Guillaume (ioguix) de Rorthais" <ioguix(at)free(dot)fr>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Raghavendra Rao J S V <raghavendrajsv(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Is there any impact if "#wal_keep_segments = 0 " and "checkpoint_segments = 128" postgresql.conf file.
Date: 2018-10-15 09:13:08
Message-ID: 20181015111308.7821dbf5@firost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 15 Oct 2018 09:46:47 +0200
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:

> Raghavendra Rao J S V wrote:
> > Is there any impact if "#wal_keep_segments = 0 " and "checkpoint_segments
> > = 128" postgresql.conf file. If yes,what is the imapct?
>
> Yes.
> - You will have fewer checkpoints requested by data modification activity.
> - Crash recovery might take longer.

And considering wal_keep_segments, there is no impact on perf/recovery. This
mostly related to the standby replication lag allowed and some other solutions
exists (slots, archiving).

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Raghavendra Rao J S V 2018-10-15 09:14:41 Re: Is there any impact if "#wal_keep_segments = 0 " and "checkpoint_segments = 128" postgresql.conf file.
Previous Message Durgamahesh Manne 2018-10-15 09:12:21 Re: Regarding varchar max length in postgres