Re: Small doc patch for pg_replication_slots

From: Thomas Reiss <thomas(dot)reiss(at)dalibo(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Small doc patch for pg_replication_slots
Date: 2014-05-01 14:42:09
Message-ID: 53625D41.4000401@dalibo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le 01/05/2014 04:56, Robert Haas a écrit :
> On Tue, Apr 29, 2014 at 5:39 AM, Thomas Reiss <thomas(dot)reiss(at)dalibo(dot)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 system catalogs. </entry>
>
> With the patch it's:
>
> <entry>The oldest transaction that this slot needs the database to
> retain. <literal>VACUUM</literal> cannot remove catalog 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
>

Thanks

--
Thomas Reiss
Consultant Dalibo
http://dalibo.com - http://dalibo.org

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2014-05-01 15:55:16 Re: Clock sweep not caching enough B-Tree leaf pages?
Previous Message Andres Freund 2014-05-01 14:12:56 Re: quiet inline configure check misses a step for clang