Re: Typo in description of replay_lag attribute in pg_stat_replication view

05.12.2018 4:04, Michael Paquier wrote: On Wed, Dec 05, 2018 at 01:24:22AM +0300, Maksim Milyutin wrote: Yeah, I think the notion *remote_flush level* is more appropriate especially in the context of sync replication. Within this context maybe it makes sense to replace the word *level* to

Re: Typo in description of replay_lag attribute in pg_stat_replication view

sense to replace the word *level* to *value* in description of *flush_lag*? -- Regards, Maksim Milyutin

Typo in description of replay_lag attribute in pg_stat_replication view

*on*. Small patch is attached. -- Regards, Maksim Milyutin diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 4164d84..33869be 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1856,7 +1856,7 @@ SELECT pid, wait_event_type, wait_event FROM

Fix links to pg_stat_replication and definition of checkpoint_warning GUC

by the definition of *checkpoint_warning* parameter, namely the phrase "caused by the filling of checkpoint segment files". I think the word "checkpoint" is unnecessary here. I tried to rephrase this definition in fix_checkpoint_warning_definition_doc.patch. -- Regards, M