Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 4C3A9632854 for ; Wed, 26 May 2010 23:24:04 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 72533-04 for ; Thu, 27 May 2010 02:23:54 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from momjian.us (momjian.us [70.90.9.53]) by mail.postgresql.org (Postfix) with ESMTP id 8A054630EB8 for ; Wed, 26 May 2010 23:23:56 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id o4R2Med27235; Wed, 26 May 2010 22:22:40 -0400 (EDT) From: Bruce Momjian Message-Id: <201005270222.o4R2Med27235@momjian.us> Subject: Re: Londiste In-Reply-To: To: Robert Haas Date: Wed, 26 May 2010 22:22:40 -0400 (EDT) CC: Francisco Reyes , Greg Sabino Mullane , pgsql-docs@postgresql.org X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.011 tagged_above=-5 required=5 tests=BAYES_40=-0.001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201005/51 X-Sequence-Number: 5548 Robert Haas wrote: > On Wed, May 26, 2010 at 5:45 PM, Bruce Momjian wrote: > > Robert Haas wrote: > >> On Tue, May 25, 2010 at 2:15 PM, Bruce Momjian wrote: > >> > Francisco Reyes wrote: > >> >> Bruce Momjian writes: > >> >> > >> >> > Well, I assumed "Londiste" head reached the level that we should mention > >> >> > it, but you are right on the floodgates issue. ?We do aleady mention > >> >> > many other replication solutions in other sections, so I didn't think > >> >> > >> >> Then perhaps all that is needed is to just link to the replication section > >> >> of the wiki: > >> >> http://wiki.postgresql.org/wiki/Replication,_Clustering,_and_Connection_Pool > >> >> ing > >> >> > >> >> A search for replication on the top of the doc page (ie > >> >> http://www.postgresql.org/docs/8.4/interactive/index.html) takes to the high > >> >> availability page, so a reference there to the wiki page may be a good idea. > >> > > >> > That is an excellent idea, not only for replication, but there are > >> > probably other wiki pages that we should link to from our main docs. ?I > >> > will go through the wiki, find appropriate pages, and add links from our > >> > docs. > >> > >> I don't know that I'm eager to link from our docs to the wiki. ?That > >> seems likely to lead to maintenance headaches. ?But on the other hand, > >> I see no problem mentioning third-party products that are part of the > >> PG ecosystem. > > > > Well, the problem is that we have more solutions that fit in the docs in > > normal places. > > Isn't that just a matter of rejiggering the page formatting a little bit? The point is that there is a lot of replication information I don't want to merge into that SGML page so even if we mention "Londiste", the wiki reference is still useful. I have the same problem with mentioning pooling in the docs --- there is no natural place to put it, but I can reference the wiki from the performance SGML docs. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com