Re: Typo in description of replay_lag attribute in pg_stat_replication view
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: milyutinma@gmail.com, pgsql-docs@lists.postgresql.org
Date: 2018-12-04T02:19:25Z
Lists: pgsql-docs
On Tue, Dec 04, 2018 at 01:28:15PM +1300, Thomas Munro wrote: > On Tue, Dec 4, 2018 at 1:18 PM Michael Paquier <michael@paquier.xyz> wrote: >> Yes, you are right. It should be "on" as "remote_flush" is not a valid >> value. remote_flush is listed in SyncCommitLevel though, so this makes >> me wonder if we should also introduce a new value for this purpose >> available for users. The fix you propose looks good to me. Any >> opinions from others? > > +1 for the patch. Thanks for confirming, Thomas. I'll go apply hopefully tomorrow if nobody has objections. > As for introducing remote_flush as the true name of the level, this > was discussed but somehow went off-course and never made it to the > finish line: > > https://www.postgresql.org/message-id/flat/CAEepm%3D3FFaanSS4sugG%2BApzq2tCVjEYCO2wOQBod2d7GWb%3DDvA%40mail.gmail.com Oh, I forgot this one. We may want to revive that... remote_flush is more meaningful than on, especially since there are more and more possible values for synchronous_commit. -- Michael
Commits
-
Fix invalid value of synchronous_commit in description of flush_lag
- db35e959bbbd 10.7 landed
- 367f362b2d90 11.2 landed
- 99f9ccee5103 12.0 landed