Hi,
Bruce Momjian wrote:
The idea being to define issues like multi/single master, async vs,
sync, and mention the projects which are in each category.
You could even add shared-nothing vs. shared-disk nodes.
Generally I'd say it makes sense to 'educate' people, but does it really
make
Thanks for mentioning about pgpool!
sect2title pgpool /title
para applicationpgpool/application was initially created by
Tatsuo Isshii as a portable alternative to Java connection pool
modules. He subsequently observed that it wouldn't take very much
effort to
Chris Browne wrote:
Here's a patch to add in the material on replication recently
discussed on pgsql.docs. I'm not thrilled that there were only a few
comments made; I'd be happy to see slicing and dicing to see this
made more useful.
The agreed-to process was
1. post information on
1. post information on pgsql-general
1.a. solicit comments
2. put information page on web site
3. link from documentation to web site
You seem to have short-circuited all that.
I don't think this sort of material belongs directly into the PostgreSQL
documentation.
It might be interesting to
Joshua D. Drake wrote:
I don't think this sort of material belongs directly into the PostgreSQL
documentation.
Why not?
It might be interesting to have some links in the external projects area
for replication, but a section of its own doesn't seem relevant.
I disagree about having some
Alvaro Herrera wrote:
Joshua D. Drake wrote:
I don't think this sort of material belongs directly into the PostgreSQL
documentation.
Why not?
Well Peter said that, not me :)
It might be interesting to have some links in the external projects area
for replication, but a section of its
Joshua D. Drake wrote:
Alvaro Herrera wrote:
Joshua D. Drake wrote:
I don't think this sort of material belongs directly into the PostgreSQL
documentation.
Why not?
Well Peter said that, not me :)
I know, but I though I'd post one message instead of two. (In fact I
didn't even think
Alvaro Herrera wrote:
I don't think this sort of material belongs directly into the
PostgreSQL documentation.
Why not?
PostgreSQL documentation (or any product documentation) should be
factual: describe what the software does and give advice on its use.
This should be mostly independent
I was thinking of something similar to our encryption section:
http://www.postgresql.org/docs/8.1/static/encryption-options.html
The idea being to define issues like multi/single master, async vs,
sync, and mention the projects which are in each category.
