http://www.slony.info/bugzilla/show_bug.cgi?id=145

           Summary: Document Mistake
           Product: Slony-I
           Version: 2.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: low
         Component: docs
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: katsumata.tomonari at oss.ntt.co.jp
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


Hi.

I've been checking the document of Slony-I.
I found some mistakes.
# I've checked the Document for 2.0.4.

The list is below.
--
[Run-time Configuration]
  - "Boolean values may be written as ON, OFF, FALSE, YES, NO, 1, 0 or
    any unambiguous prefix of these."
    ... I think it's natural including "TRUE".


[Slonik Command Summary]
  - "psqllacks the ability to maintain multiple connections with open
ransactions."
    ... It should start with "psql lacks the ability ..."


[Log Analysis]
  - "・DEBUG3: remoteWorkerThread_%d: table %s Slony-I serial key added local
     ・DEBUG2: remoteWorkerThread_%d: Begin COPY of table %s"
    ... It should be explanation for these log messages.

  - "・DEBUG1: remoteWorkerThread_%d: copy_set %d done in %.3f seconds
       Indicates the total time required to complete copy_set... This indicates
       a successful subscription!

     ・DEBUG1: remoteWorkerThread_%d: copy_set %d done in %.3f seconds
       Indicates the total time required to complete copy_set... This indicates
       a successful subscription!"
    ... above sentences are same.

  - "These events should occur frequently and routinely as nodes report
     confirations of the events they receive."
    ... type miss? "confirations" --> "confirmations"

  - "This would typically happen if you submit SLONIK STORE NODE gainst
     a node that has already been set up with the Slony-I schema. "
    ... type miss? "gainst" --> "against"

[Slon daemons]
  - "One slon service is installed, and a seperate configuration file
     registered for each node to be serviced by that machine."
    ... type miss? "seperate" --> "separate"


[Subscribing Nodes]
  - "In that failure case, that subscriber node will never pick up the
subscriber."
    ... Is this sentence right? I think "the subscriber" is "the provider".


[Doing swtchover and failover with Slony-I]
  - "Resubscribe (using SLONIK SUBSCRIBE SET ech node that is to be kept in the
     reformation of the cluster that is not already subscribed to the intended
     data provider."
    ... lack of ")" after "SUBSCRIBE SET".
        and type miss? "ech" --> "each"


[Defining Slony-I Clusters]
  - "Note that, as recorded in the "" under How can I renumber nodes?,
     the node number is immutable, so it is not possible to change a node's
     node number after it has been set up."
    ... What does "" mean ? I think it's "FAQ", right?


[Reshaping a Cluster]
  - "If you want a node that is a subscriber to become the origin for a
     particular replication set, you will have to issue a suitable slonik
     MOVE SET operation."
    ... "slonik" is linkied to another page.
        It should be linked "SLONIK MOVE SET" page.


[Log Shipping - Slony-I with Files]
  - "Optional conninfo for the destination database. If given, the log shipper
     will connect to thisdatabase, and apply logs to it."
    ... type miss? "thisdatabase" --> "this database"

  - "Pre- and post-processign commands are executed via system(3). "
    ... type miss? "processign" --> "processing"

  - "Similarly, SET_DROP_TABLE, SET_DROP_SEQUENCE, SET_MOVE_TABLE,
     SET_MOVE_SEQUENCE DROP_SET, MERGE_SET, will be handled "appropriately"."
    ... It should be comma between "SET_MOVE_SEQUENCE" and "DROP_SET".


[Defining Slony-I Replication Sets]
  - "If your application is not somehow referencing the index by name,
     the this should not lose you anything, and it gives you the clear design
     benefit that a primary key has been declared for the table."
    ... type miss? "the" --> "then"


[Slony-I Path Communications]
  - "DB5 and and DB6 are counterparts to DB1 and DB2, but are, at present,
     configured as subscribers."
    ... "and" is doubled.


[Slony-I listen paths]
  - "it gets events for nodes 1, 3, and 4 throw node 1, and gets events
     for nodes 5 and 6 from node 5."
    ... type miss? "throw" --> "through"

  - "Until Slony-I, there is no automated way at this point to do this
"reshaping"."
    ... I dont't know which Slony-I version.


[SLONIK MERGE SET]
  - "# Assuming that set 1 has direct subscribers 2 and 3"
    ... I think "provider 1" is better than "set 1".


[SLONIK STORE NODE]
  - "The SPOOLNODE parameter was introduced in version 1.1, but was vestigal
     in that version. "
    ... type miss? "vestigal" --> "vestigial"


[SLONIK TABLE ADD KEY]
  - "That leaves the "kludgy" columns created via TABLE ADD KEY as the only
     thing that prevents SLONIK UNINSTALL NODE from being comprised of the SQL
     statement drop schema _ClusterName cascade;."
    ... type miss? "kludgy" --> "kludgey"


[SLONIK WAIT FOR EVENT]
  - "# Assuming that set 1 has direct subscribers 2 and 3"
    ... I think "provider 1" is better than "set 1".


[Slony-I FAQ]
  - "Node 3 - subscriber to node 3 - node that should keep replicating"
    ... I think "node 3" is better than "node 3".

--

Sorry for late reporting.
Please check them.

regards,
----------
Tomonari Katsumata
NTT Open Source Software Center
E-Mail: katsumata.tomonari at oss.ntt.co.jp

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.