From: | Jason Ralph <jralph(at)affinitysolutions(dot)com> |
---|---|
To: | Benoit Lobréau <benoit(dot)lobreau(at)gmail(dot)com>, Luca Ferrari <fluca1978(at)gmail(dot)com> |
Cc: | "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-07 00:15:54 |
Message-ID: | BL0PR04MB6499BE55F07D19FCF3AD4030D0B50@BL0PR04MB6499.namprd04.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks,
I currently have the systems running a parallel pg_dump each night to a separate partition mounted on the VM. Then I perform a full backup of the VM and all mounted drives each night. Would this be affected by disabling wal archiving? I noted that I understood wal archiving was affected in my initial question. But I was not able to see how it could affect my setup. Please school me if I am being naive.
Jason Ralph
________________________________
From: Benoit Lobréau <benoit(dot)lobreau(at)gmail(dot)com>
Sent: Friday, September 6, 2019 3:41:44 AM
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
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<mailto:fluca1978(at)gmail(dot)com>> a écrit :
On Wed, Sep 4, 2019 at 10:44 PM Jason Ralph
<jralph(at)affinitysolutions(dot)com<mailto: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
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
From | Date | Subject | |
---|---|---|---|
Next Message | Ali Alizadeh | 2019-09-07 04:35:52 | Convert a row to a nested JSON document containing all relations in PostgreSQL |
Previous Message | Adrian Klaver | 2019-09-06 22:39:54 | Re: pg_restore issues with intarray |