Mon Oct 22 13:44:26 PDT 2007
- Previous message: [Slony1-commit] slony1-engine/tests/testmergeset gen_ddl_slonik.sh init_subscribe_set.ik schema.diff
- Next message: [Slony1-commit] slony1-engine/src/slon remote_worker.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine In directory main.slony.info:/tmp/cvs-serv19826 Modified Files: Tag: REL_1_2_STABLE RELEASE Log Message: - Error handling for "ERROR: could not serialize access due to concurrent update" If this error is encountered when starting processing of sl_archive_counter, then two threads are fighting over access to this counter, and at least one has just failed. Rather than waiting, we ask to restart the node immediately. Index: RELEASE =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/RELEASE,v retrieving revision 1.1.2.18 retrieving revision 1.1.2.19 diff -C2 -d -r1.1.2.18 -r1.1.2.19 *** RELEASE 4 Oct 2007 15:22:40 -0000 1.1.2.18 --- RELEASE 22 Oct 2007 20:44:24 -0000 1.1.2.19 *************** *** 9,12 **** --- 9,17 ---- do no work when not specifically requested. + CAVEAT: This functionality may not work as expected on versions + of PostgreSQL earlier than 8.1. Mind you, partitioning tends + to function pretty poorly in earlier versions of PostgreSQL as + there were substantial enhancements in 8.1 and following versions. + - Added a fairly substantial partitioning test to exercise the new stored functions above. *************** *** 20,26 **** SERIALIZABLE;" query that needs to be the first thing run... ! - Fixing the archive sequence generations. All non-SYNC events must ! start the local transaction before creating the archive as well, so ! that the lock on the archive counter table serializes archive creation. - Fixed logging done in local_listener.c - various places, there was --- 25,32 ---- SERIALIZABLE;" query that needs to be the first thing run... ! - Fixing the archive sequence generations (in log shipping). All ! non-SYNC events must start the local transaction before creating the ! archive as well, so that the lock on the archive counter table ! serializes archive creation. - Fixed logging done in local_listener.c - various places, there was *************** *** 30,33 **** --- 36,48 ---- - Fix launch_slons.sh - was not stripping quotes from PID file name + - Error handling for "ERROR: could not serialize access due to + concurrent update" + + If this error is encountered when starting processing of + sl_archive_counter, then two threads are fighting over access to + this counter, and at least one has just failed. + + Rather than waiting, we ask to restart the node immediately. + RELEASE 1.2.11
- Previous message: [Slony1-commit] slony1-engine/tests/testmergeset gen_ddl_slonik.sh init_subscribe_set.ik schema.diff
- Next message: [Slony1-commit] slony1-engine/src/slon remote_worker.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list