Re: Small doc patch for pg_replication_slots - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Small doc patch for pg_replication_slots
Date
Msg-id CA+TgmoYmf7bA47br3H+nxyPe9Kk9FAD-J7pWFwWvGAdGB-+iWw@mail.gmail.com
Whole thread Raw
In response to Small doc patch for pg_replication_slots  (Thomas Reiss <thomas.reiss@dalibo.com>)
Responses Re: Small doc patch for pg_replication_slots  (Thomas Reiss <thomas.reiss@dalibo.com>)
List pgsql-hackers
On Tue, Apr 29, 2014 at 5:39 AM, Thomas Reiss <thomas.reiss@dalibo.com> wrote:
> You can find attached a small patch to fix the pg_replication_slots
> documentation. The slot_type and plugin are not in the appropriate
> order, slot_name and plugin have a wrong type and xmin appears two times.

Without the patch, the description of catalog_xmin is:
     <entry>The <literal>xmin</literal>, or oldest transaction ID, that this     slot forces to be retained in the
systemcatalogs. </entry>
 

With the patch it's:
     <entry>The oldest transaction that this slot needs the database to     retain.  <literal>VACUUM</literal> cannot
removecatalog tuples deleted     by any later transaction.
 

That's only one word different from the language for xmin, which
doesn't seem quite right.  Committed after fixing that.

...Robert



pgsql-hackers by date:

Previous
From: Gavin Flower
Date:
Subject: Re: Display of timestamp in pg_dump custom format
Next
From: Michael Paquier
Date:
Subject: Re: hooks not working in postgresql 9.3 (building from source)