| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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-07 21:59:24 |
| Message-ID: | 78ff5cc9-268f-4be8-ae0b-c1a07dc24852@proxel.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/4/26 4:55 PM, David G. Johnston wrote:
> In evaluating the proposed change to wal_level docs in [1] I found it to
> be undesirable, but the discussion and my own review discovered some
> other changes that should be considered.
While I am not happy with the text before I am not sure your changes
here really make it much better, just different, hmm.
> Since effective_wal_level now exists, Logical Replication Getting
> Started needs to be updated.
> Add links to the main topics that the different levels apply to.
> Be explicit about the ordering of minimal, replica, and logical.
> Move the behavior of effective_wal_level to the GUC for it, leaving
> behind just the pointer that wal_level is now just a "minimum".
Shouldn't it be:
"Ensure that <xref linkend="guc-wal-level"/> is at least replica"
and
"wal_level = replica"
as the logical replication slot may be created later?
--
Andreas Karlsson
Percona
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-04-07 22:05:47 | Re: pg_plan_advice |
| Previous Message | Andres Freund | 2026-04-07 21:52:31 | Re: EXPLAIN: showing ReadStream / prefetch stats |