Mon Aug 9 14:09:17 PDT 2010
- Previous message: [Slony1-bugs] [Bug 142] Minimize security profile
- Next message: [Slony1-bugs] [Bug 148] New: TablesToVacuum tries to vacuum pg_listener which no longer exists in 9.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=134 --- Comment #4 from Christopher Browne <cbbrowne at ca.afilias.info> 2010-08-09 14:09:17 PDT --- Thinking about implementation... We could: a) Try to capture the trigger using the existing C/SPI function. That seems like overkill, as we don't need to collect data. b) Create a trigger function that captures the table ID as its argument, and uses that to determine which table to truncate. Consistent with the preceding discussion, I propose using "policy #4" to handle this, that is, on replicated nodes, we'll run, for each table: truncate ONLY my_table CASCADE; -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 142] Minimize security profile
- Next message: [Slony1-bugs] [Bug 148] New: TablesToVacuum tries to vacuum pg_listener which no longer exists in 9.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list