public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Robert Haas <[email protected]>
Cc: Francisco Reyes <[email protected]>
Cc: Greg Sabino Mullane <[email protected]>
Cc: [email protected]
Subject: Re: Londiste
Date: Wed, 26 May 2010 17:45:15 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Robert Haas wrote:
> On Tue, May 25, 2010 at 2:15 PM, Bruce Momjian <[email protected]> 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.  I was thinking of just linking to major wiki pages, like
replication and pooling.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

view thread (20+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Londiste
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox