There has been some recent discussion on the slony -general mailing list about what changes should be made in the next major version of slony.
The slony team would like to get a sense of what aspects of slony are causing people issues or what features need to be added. The idea list is being tracked in a wiki page.
Some of the ideas being floated around include:
Improve the performance of replicating Slony over a WAN with high lag
Allow you to specify multilple tables to replicate in from a single slonik command. (ie set add table(tables=’public.*’)
Allow you to specify which tables EXECUTE SCRIPT should lock on the command line
Make it easier to see what each slon is currently working on and how many statements need to be replicated to a particular host without having to scan log files
Make slonik automatically ‘WAIT FOR’ commands that execute asynchronously
Replicate DDL automatically (yes, this requires DDL trigger triggers to be added to PostgreSQL
If your using slony and see a need for these (or any other changes) I’d appreciate it if you let me know what your top 3 requests are (leave a comment, drop a note to the slony mailing list or email me).
Like this:
Like Loading...
Related
Scanning Pages 
My top 3:
#1: Replicate DDL automatically
#2: Improve the performance of replicating Slony over a WAN with high lag
#3: Make it easier to see what each slon is currently working on and how many statements need to be replicated to a particular host without having to scan log files
🙂
I would really like to specify the different keepalive parameters used by slony. At the moment, we often have to restart slon after a network outage/server down/etc.