[Pgcluster-general] pgcluster patch
Markus Schmidleitner
markus.schmidleitner at ocilion.com
Thu Apr 30 15:00:00 UTC 2009
hello list, hello mitani!
@mitani
great, you're back!!
thank's a lot for this awsome piece of software - great work - keep it
up!
@all
maybe someone recognized the 'cybercluster-backport and more'-patch and
the 'replication-server-failover'-patch i sent in a while ago.
here's another patch-set based on the 2 patches before.
the current patch-set is against postgresql 8.3.7.
i hope anyone will give it a try.
comments/suggestions are highly appreciated!
@mitani
maybe you can do some code review/testing on it? would be nice ;-)
changes regarding to previous patches:
- initdb now works as expected (failed in previous patches)
- added postgresql startup parameter '-a' to set the cluster in full
standalone mode, bypassing all replication operations (mainly for
regression testing and an operational mode which we need here)
- added a few configuration parameters (see current cluster.conf and
pgreplicate.conf)
- now you can specify a comma separated list of hostnames or addresses
in Host_Name-Parameter (currently this is limited to a set of 2 - see
cluster.conf and pgreplicate.conf)
- pgreplicate and postgresql recovery processes now listen only on those
interfaces that are specified
- set default-value of auto_lock_table to false
- reworked locking code and deadlock notification
- some refinements on networking-code
- use modified elog instead of own logging-code (mainly for logging in
common code used by pgreplicate and postgresql - currently logging from
pgreplicate to a logfile is not implemented)
- some more general reworks, dead code eliminations ...
changes from earlier patches:
- replication server will be noticed to all clusters
- cluster will be noticed to all replication servers
- standby replication server send cascade info to cluster
* cluster will automatically switch to primary replication server
- primary replication server requests replication servers from cluster
* replication server will automatically setup cascade
* clusters automatically switch back to primary replication server
- added threading-support in pgreplicate (mainly backported from
cybercluster)
- code refactoring
* implemented functions for non-blocking i/o which are used by entire
pgcluster
* all net-i/o operations are non-blocking
* earse dead code
* remove needless memcpy
* other minor reworks
- implemented a cluster-notice message when cascading is used
* it informs the upper and lower cascade that cluster finished
recovery and can be used now
best regards,
Markus Schmidleitner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postgresql-8.3.7-src-to-pgcluster-1.9.11-src.patch
Type: text/x-patch
Size: 1118006 bytes
Desc: not available
Url : http://pgfoundry.org/pipermail/pgcluster-general/attachments/20090430/6e444885/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postgresql-8.3.7-to-pgcluster-1.9.11.patch
Type: text/x-patch
Size: 31222 bytes
Desc: not available
Url : http://pgfoundry.org/pipermail/pgcluster-general/attachments/20090430/6e444885/attachment-0003.bin
More information about the Pgcluster-general
mailing list