Thu Feb 14 12:49:36 PST 2008
- Previous message: [Slony1-bugs] [Bug 34] slonik crash if spoolnode = true
- Next message: [Slony1-bugs] [Bug 34] slonik crash if spoolnode = true
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=34 Christopher Browne <cbbrowne at ca.afilias.info> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Christopher Browne <cbbrowne at ca.afilias.info> 2008-02-14 12:49:36 --- The way that log shipping functions has changed from the time when we anticipated that this "SPOOLNODE" slonik parameter would be used to control initializing log shipping nodes. When I try to replicate this, I find that the slonik script that tries to set SPOOLNODE=TRUE falls over with a segfault... I'll point out three things: 1. SPOOLNODE=true has never actually been usable in any Slony-I release. There was a plan to have "log shipping nodes" visible in the configuration, but the way they were eventually implemented, this is no longer necessary. There isn't yet a really good tutorial on using logshipping, but see the following: http://slony.info/documentation/logshipping.html - has a lot of relevant notes, (none of which suggest setting SPOOLNODE=true). There is a logshipping test; see the sources in CVS: http://main.slony.info/viewcvs/viewvc.cgi/slony1-engine/tests/testlogship/?pathrev=REL_1_2_STABLE This is a functioning test; reviewing the code, particularly in "generate_dml.sh", should be helpful in seeing what steps are needed to set up a log shipping node. 2. I'm patching 1_2_STABLE to indicate an error message, if SPOOLNODE=true, as follows: cbbrowne at dba2:CMD/slony1-1.2/src/slonik> cvs diff -u cvs diff: Diffing . Index: slonik.c =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/src/slonik/slonik.c,v retrieving revision 1.67.2.13 diff -c -u -r1.67.2.13 slonik.c cvs diff: conflicting specifications of output style --- slonik.c 8 Jan 2008 20:42:41 -0000 1.67.2.13 +++ slonik.c 14 Feb 2008 20:44:42 -0000 @@ -327,6 +327,10 @@ if (!stmt->no_spool) { + printf("Slonik command STORE NODE does not " + "support the SPOOLNODE argument being set " + "to TRUE.\n See logshipping.html for " + "documentation on setting up log shipping.\n"); if (script_check_adminfo(hdr, stmt->no_id) < 0) errors++; } 3. SPOOLNODE-related code should get cleaned out altogether in CVS HEAD. -- 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.
- Previous message: [Slony1-bugs] [Bug 34] slonik crash if spoolnode = true
- Next message: [Slony1-bugs] [Bug 34] slonik crash if spoolnode = true
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list