Thread: PG11.2 - wal_level =minimal max_wal_senders = 0

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.

On Wed, Sep 4, 2019 at 5:15 PM Jason Ralph <jralph@affinitysolutions.com> wrote:
> The question I have is, for a production database not doing replication, can I safely set the following parameters, I
understandthat minimal will also disable wal_archiving so I am concerned about that as well. 
>
> wal_level = minimal
>
> max_wal_senders = 0
>
>
>
> I have been looking at the documentation and I guess I am looking for a yes this is ok, I figured it’s on by default
fora reason so I was hesitant to change it. 

I don't see why you should not set them as you described.
The idea is that the overhead of having replica over minimal is today
enough "low" in contrast to the need for replication (e.g., backup
tools like pgbackrest).

Luca

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
processvia the setting below? In my sandbox it does turn off the logical replication launcher, I just wanted to be sure
Iam not affecting anything other than replication with this setting.
 


max_logical_replication_workers = 0     # taken from max_worker_processes
                                        # (change requires restart)


Jason Ralph

-----Original Message-----
From: Luca Ferrari <fluca1978@gmail.com>
Sent: Wednesday, September 4, 2019 12:16 PM
To: Jason Ralph <jralph@affinitysolutions.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: PG11.2 - wal_level =minimal max_wal_senders = 0

On Wed, Sep 4, 2019 at 5:15 PM Jason Ralph <jralph@affinitysolutions.com> wrote:
> The question I have is, for a production database not doing replication, can I safely set the following parameters, I
understandthat minimal will also disable wal_archiving so I am concerned about that as well.
 
>
> wal_level = minimal
>
> max_wal_senders = 0
>
>
>
> I have been looking at the documentation and I guess I am looking for a yes this is ok, I figured it’s on by default
fora reason so I was hesitant to change it.
 

I don't see why you should not set them as you described.
The idea is that the overhead of having replica over minimal is today enough "low" in contrast to the need for
replication(e.g., backup tools like pgbackrest).
 

Luca
This message contains confidential information and is intended only for the individual named. If you are not the named
addresseeyou should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if
youhave received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be
guaranteedto 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
contentsof this message, which arise as a result of e-mail transmission. If verification is required please request a
hard-copyversion.
 

On Wed, Sep 4, 2019 at 10:44 PM Jason Ralph
<jralph@affinitysolutions.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
processvia the setting below? In my sandbox it does turn off the logical replication launcher, I just wanted to be sure
Iam 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.

On Sat, Sep 7, 2019 at 2:15 AM Jason Ralph <jralph@affinitysolutions.com> wrote:
> I currently have the systems running a parallel pg_dump each night to a separate partition mounted on the VM. Then I
performa full backup of the VM and all mounted drives each night. Would this be affected by disabling wal archiving? I
notedthat I understood wal archiving was affected in my initial question. But I was not able to see how it could affect
mysetup. Please school me if I am being naive. 

No, if you are using pg_dump you are not affected by archiving.
Archiving is used to backup with tools like pgbackrest, barman, wal-e
and alike. If you are running your database isolated (i.e., no slaves,
no advanced backups), running it without replication level in wal and
using only pg_dump is fine.

Luca