From: | Benoit Lobréau <benoit(dot)lobreau(at)gmail(dot)com> |
---|---|
To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
Cc: | Jason Ralph <jralph(at)affinitysolutions(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PG11.2 - wal_level =minimal max_wal_senders = 0 |
Date: | 2019-09-06 07:41:44 |
Message-ID: | CAPE8EZ4=WcyWW49NtQWkXC70fuqW6o=VAnj-BEJ_4eW_=1UpTA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
Make sure that the new settings of wal_level and max_wal_senders don't
interfere with your backup strategy.
The two parameters have an impact on wal archiving as well.
Ben.
Le jeu. 5 sept. 2019 à 08:33, Luca Ferrari <fluca1978(at)gmail(dot)com> a écrit :
> On Wed, Sep 4, 2019 at 10:44 PM Jason Ralph
> <jralph(at)affinitysolutions(dot)com> wrote:
> >
> > Thank you Luca,
> > Can I ask one more related question, I have no need for replication as
> noted below, can I safely disable the worker process via the setting below?
> In my sandbox it does turn off the logical replication launcher, I just
> wanted to be sure I am not affecting anything other than replication with
> this setting.
> >
> >
> > max_logical_replication_workers = 0 # taken from max_worker_processes
> > # (change requires restart)
> >
>
> Quite frankly I've never done, but I don't see why you should not turn it
> off.
>
> Luca
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick FICHE | 2019-09-06 09:06:04 | Primary Key Update issue ? |
Previous Message | Stacey Haysler | 2019-09-06 06:20:47 | Seeking New Members for the Community Code of Conduct Committee |