| From: | Raghavendra Rao J S V <raghavendrajsv(at)gmail(dot)com> |
|---|---|
| To: | ioguix(at)free(dot)fr |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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:14:41 |
| Message-ID: | CAEHH7R6go_JyOYoKyazZhAR3vDte1HtLadVxL4_L41Es08OXnA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks a lot.
On Mon, 15 Oct 2018 at 14:43, Jehan-Guillaume (ioguix) de Rorthais <
ioguix(at)free(dot)fr> wrote:
> 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).
>
--
Regards,
Raghavendra Rao J S V
Mobile- 8861161425
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Durgamahesh Manne | 2018-10-15 09:18:32 | Re: Regarding varchar max length in postgres |
| Previous Message | Jehan-Guillaume (ioguix) de Rorthais | 2018-10-15 09:13:08 | Re: Is there any impact if "#wal_keep_segments = 0 " and "checkpoint_segments = 128" postgresql.conf file. |