| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | doc: Improve wal_level and effective_wal_level GUC around logical replication |
| Date: | 2026-03-04 15:55:13 |
| Message-ID: | CAKFQuwY=WLF0OH8JE5T8S=aj0LBydiSn02fkRE73Sm_KSLRqJQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
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.
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".
David J.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-doc-Add-some-clarity-around-wal_level.patch | text/x-patch | 6.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-03-04 15:55:58 | Re: Don't keep closed WAL segment in page cache after replay |
| Previous Message | Andrew Dunstan | 2026-03-04 15:51:14 | Re: Emitting JSON to file using COPY TO |