Sun May 16 05:39:46 PDT 2010
- Previous message: [Slony1-hackers] [Slony1-general] [Slony1-bugs] Slony triggers included in pg_dump
- Next message: [Slony1-hackers] Subscribe set question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi All, Attached is a patch of 2.0.3 with the following: 1) New script slonik_add_node. This adds the capability to add a node to the cluster. This node could be from the fact that the config file was edited to add new node's info, or maybe it was previously dropped from the cluster. 2) An enhancement to the slonik_drop_node script. The original version assumed that $MASTERNODE is available for this operation to complete, but that might not always be the case. Now one needs to specify an event_node# which should be capable of sending the event notification to other nodes in the cluster. For backward compatibility the new parameter can be made optional. 3) A minor improvement to the message emitted by slon_kill, to differentiate between when the Slon processes are being killed vs. when the watchdog processes are being killed. Regards, -- gurjeet.singh @ EnterpriseDB - The Enterprise Postgres Company http://www.enterprisedb.com singh.gurjeet@{ gmail | yahoo }.com Twitter/Skype: singh_gurjeet Mail sent from my BlackLaptop device -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-hackers/attachments/20100516/2d332c33/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: slony1-2.0.3.patch Type: application/octet-stream Size: 6213 bytes Desc: not available Url : http://lists.slony.info/pipermail/slony1-hackers/attachments/20100516/2d332c33/attachment.obj
- Previous message: [Slony1-hackers] [Slony1-general] [Slony1-bugs] Slony triggers included in pg_dump
- Next message: [Slony1-hackers] Subscribe set question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-hackers mailing list