From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Thom Brown <thom(at)linux(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Various typo fixes |
Date: | 2023-04-12 03:28:25 |
Message-ID: | ZDYlWcycBimwEtuU@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 11, 2023 at 11:12:58PM +0200, Daniel Gustafsson wrote:
> > On 11 Apr 2023, at 16:53, Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
>
> > I think "logical" should be a <literal> here.
>
> Agree, it should in order to be consistent.
Indeed.
+ to the wal_level parameter change on the primary won't be decoded.
This wal_level should also have a markup.
Number of uses of logical slots in this database that have been
- canceled due to old snapshots or a too low <xref linkend="guc-wal-level"/>
+ canceled due to old snapshots or too low a <xref linkend="guc-wal-level"/>
This sounds a bit strange to me. A too low wal_level would be a cause
for a cancel, hence shouldn't this be "canceled due to old snapshots
or due to a too low guc-wal-level?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2023-04-12 03:44:43 | Re: Various typo fixes |
Previous Message | Thomas Munro | 2023-04-12 03:04:16 | Re: Direct I/O |