Re: [HACKERS] [PATCHES] Replication Documentation
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 sense to explain all that if there is no replication solution for most of these combinations? I'd vote for an external (not in the documentation) information site about replication solutions. There we can put all the information we see fit (even 'journalistic' ones). I might change my mind once we have multiple replication solutions covering most situations. ;-) I like what and how Chris wrote [1] - an overview over existing and upcomming replication solutions. Regards Markus [1]: I can't find Chris' original message. My answer to it is in the archives, but not the original message. Why is that? (Thread view says 'message not available'). My answer contains Chris' text, though: http://archives.postgresql.org/pgsql-docs/2006-07/msg00019.php ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [HACKERS] [PATCHES] Replication Documentation
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 extend it to create a simple replication system: if it is forwarding SQL queries to a PostgreSQL instance, extending that to two databases is very straightforward. /para para It suffers, by nature, from the problems associated with replicating using capture of SQL statements; any sort of nondeterminism in the replicated statements will cause the databases to diverge. /para para On the other hand, it is very easy to install and configure; for users with simple requirements, that can suffice. /para para A applicationpgpool-2/application is under way which introduces a more sophisticated query parser to try to address the nondeterminism issues; that may limit ongoing support for the legacy version./para pgpool-II (not pgpool-2, please) does not try to resolve nondeterminism issues but try to add parallel SELECT query execution. Also we will continue to support legacy version until pgpool-II becomes stable enough. Also you might want to add pgpool development site URL. FYI, pgpool-II presentation material for PostgreSQL Anniversary Summit can be obtained from: http://www.sraoss.co.jp/event_seminar/2006/pgpool_feat_and_devel.pdf -- Tatsuo Ishii SRA OSS, Inc. Japan ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] [PATCHES] Replication Documentation
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 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. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [PATCHES] Replication Documentation
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 have some links in the external projects area for replication, but a section of its own doesn't seem relevant. Joshua D. Drkae -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] [PATCHES] Replication Documentation
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 links. Maybe we should consider adding this as a section in the external projects chapter, instead of having a chapter of its own, but some links seems a little short on actual contents. -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] [PATCHES] Replication Documentation
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 own doesn't seem relevant. I disagree about having some links. Maybe we should consider adding this as a section in the external projects chapter, instead of having a chapter of its own, but some links seems a little short on actual contents. O.k. more specifically, I think that the content (even if it is a section) probably deserves discussion in the external projects section. Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] [PATCHES] Replication Documentation
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 about it -- I just assume it's clear.) 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 links. Maybe we should consider adding this as a section in the external projects chapter, instead of having a chapter of its own, but some links seems a little short on actual contents. O.k. more specifically, I think that the content (even if it is a section) probably deserves discussion in the external projects section. Sure, see my suggestion above. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [PATCHES] Replication Documentation
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 of the external circumstances, because people will still read that documentation three or four years from now. The proposed text is, at least partially, journalistic: it evaluates competing ideas, gives historical and anecdotal information, reports on current events, and makes speculations about the future. That is the sort of material that is published in periodicals or other volatile media. At the summit, we resolved, for precisely these reasons, to keep the journalistic parts on the web site, for clear separation from the shipped product and for easier updates (and for easier reference as well, because the PostgreSQL documentation is not the single obvious place to look for it) and refer to it from the documentation. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] [PATCHES] Replication Documentation
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. --- Peter Eisentraut wrote: 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 of the external circumstances, because people will still read that documentation three or four years from now. The proposed text is, at least partially, journalistic: it evaluates competing ideas, gives historical and anecdotal information, reports on current events, and makes speculations about the future. That is the sort of material that is published in periodicals or other volatile media. At the summit, we resolved, for precisely these reasons, to keep the journalistic parts on the web site, for clear separation from the shipped product and for easier updates (and for easier reference as well, because the PostgreSQL documentation is not the single obvious place to look for it) and refer to it from the documentation. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly