Thu Jul 29 14:46:46 PDT 2004
- Previous message: [Slony1-general] sl_event.ev_type: ENABLE_NODE, but no DISABLE_NODE
- Next message: [Slony1-general] sl_event.ev_type: ENABLE_NODE, but no DISABLE_NODE
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Justin Clift <jc at telstra.net> writes: > Hi all, > > Am going through the Slony tables, documenting what they do in order > to get a feel for how things hang together. > > Noticed that sl_event.ev_type has this range of values: > > SYNC > STORE_NODE > ENABLE_NODE > DROP_NODE > STORE_PATH > DROP_PATH > STORE_LISTEN > DROP_LISTEN > STORE_SET > DROP_SET > MERGE_SET > SET_ADD_TABLE > SET_ADD_SEQUENCE > STORE_TRIGGER > DROP_TRIGGER > MOVE_SET > FAILOVER_SET > SUBSCRIBE_SET > ENABLE_SUBSCRIPTION > UNSUBSCRIBE_SET > DDL_SCRIPT > ADJUST_SEQ Hmm. I'd be game to create a descriptive table for that, and have sl_event point to that as a "foreign key" validation... -- select 'cbbrowne' || '@' || 'ca.afilias.info'; <http://dev6.int.libertyrms.com/> Christopher Browne (416) 673-4124 (land)
- Previous message: [Slony1-general] sl_event.ev_type: ENABLE_NODE, but no DISABLE_NODE
- Next message: [Slony1-general] sl_event.ev_type: ENABLE_NODE, but no DISABLE_NODE
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list