Thu Oct 14 23:17:51 PDT 2004
- Previous message: [Slony1-commit] By cbbrowne: Added docs for SET_MOVE_TABLE and SET_MOVE_SEQUENCE
- Next message: [Slony1-commit] By darcyb: Don't step past the end of the passed in conn_info
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message: ----------- Added documentation for SET_MOVE_TABLE and SET_MOVE_SEQUENCE functions and events Modified Files: -------------- slony1-engine/src/backend: README.events (r1.3 -> r1.4) slony1_base.sql (r1.18 -> r1.19) slony1_funcs.sql (r1.33 -> r1.34) -------------- next part -------------- Index: slony1_base.sql =================================================================== RCS file: /usr/local/cvsroot/slony1/slony1-engine/src/backend/slony1_base.sql,v retrieving revision 1.18 retrieving revision 1.19 diff -Lsrc/backend/slony1_base.sql -Lsrc/backend/slony1_base.sql -u -w -r1.18 -r1.19 --- src/backend/slony1_base.sql +++ src/backend/slony1_base.sql @@ -275,6 +275,8 @@ MOVE_SET = SET_DROP_TABLE = SET_DROP_SEQUENCE = + SET_MOVE_TABLE = + SET_MOVE_SEQUENCE = FAILOVER_SET = SUBSCRIBE_SET = ENABLE_SUBSCRIPTION = Index: README.events =================================================================== RCS file: /usr/local/cvsroot/slony1/slony1-engine/src/backend/README.events,v retrieving revision 1.3 retrieving revision 1.4 diff -Lsrc/backend/README.events -Lsrc/backend/README.events -u -w -r1.3 -r1.4 --- src/backend/README.events +++ src/backend/README.events @@ -144,6 +144,28 @@ Only nodes that are currently subscribed to the sequence will drop the table from their configuration data. +SET_MOVE_TABLE + ev_data1 tab_id + ev_data2 set_id + + setMoveTable(tab_id, new_set_id) + setMoveTable_int(tab_id, new_set_id) + + Only nodes currently subscribed to the table will drop it from + one set, and move it to another. + +SET_MOVE_SEQUENCE + ev_data1 seq_id + ev_data2 set_id + + setMoveSequence(seq_id, new_set_id) + setMoveSequence_int(seq_id, new_set_id) + + + Only nodes currently subscribed to the sequence will drop it + from one set, and move it to another. + + SUBSCRIBE_SET ev_data1 sub_set ev_data2 sub_provider Index: slony1_funcs.sql =================================================================== RCS file: /usr/local/cvsroot/slony1/slony1-engine/src/backend/slony1_funcs.sql,v retrieving revision 1.33 retrieving revision 1.34 diff -Lsrc/backend/slony1_funcs.sql -Lsrc/backend/slony1_funcs.sql -u -w -r1.33 -r1.34 --- src/backend/slony1_funcs.sql +++ src/backend/slony1_funcs.sql @@ -2814,6 +2814,11 @@ end; ' language plpgsql; +comment on function @NAMESPACE at .setMoveTable(int4,int4) is +'This generates the SET_MOVE_TABLE event. If the set that the table is +in is identically subscribed to the set that the table is to be moved +into, then the SET_MOVE_TABLE event is raised.'; + -- ---------------------------------------------------------------------- -- FUNCTION setMoveTable_int (tab_id, new_set_id) @@ -2842,7 +2847,9 @@ return p_tab_id; end; ' language plpgsql; - +comment on function @NAMESPACE at .setMoveTable(int4,int4) is +'This processes the SET_MOVE_TABLE event. The table is moved +to the destination set.'; -- ---------------------------------------------------------------------- -- FUNCTION setMoveSequence (seq_id, new_set_id)
- Previous message: [Slony1-commit] By cbbrowne: Added docs for SET_MOVE_TABLE and SET_MOVE_SEQUENCE
- Next message: [Slony1-commit] By darcyb: Don't step past the end of the passed in conn_info
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list