Re: doc: Improve wal_level and effective_wal_level GUC around logical replication

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Andreas Karlsson <andreas(at)proxel(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: doc: Improve wal_level and effective_wal_level GUC around logical replication
Date: 2026-04-08 03:27:54
Message-ID: CAKFQuwb3dG_tLFbWc_A_NMu-1b7xfGhPBa=dnAGptBT_CNBqLw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday, April 7, 2026, Andreas Karlsson <andreas(at)proxel(dot)se> wrote:

>
> Since effective_wal_level now exists, Logical Replication Getting Started
>> needs to be updated.
>>
>> Shouldn't it be:
>
> "Ensure that <xref linkend="guc-wal-level"/> is at least replica"
>

Given “at least” it is immaterial whether one inspects wal_level or
effective_wal_level. It seems more intuitive to tell someone to look at
the value that represents what the system presently is using, not the
defined minimum level.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-04-08 03:36:19 Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion?
Previous Message Xuneng Zhou 2026-04-08 03:23:54 Re: Implement waiting for wal lsn replay: reloaded