Thu Jun 9 12:37:07 PDT 2011
- Previous message: [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble
- Next message: [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=217 --- Comment #14 from Steve Singer <ssinger at ca.afilias.info> 2011-06-09 12:37:08 PDT --- (In reply to comment #13) > Maybe we aren't supposed to query pg_trigger, but query the > information_schema.triggers view instead? > > > Jan The information schema gives rows like EXECUTE PROCEDURE _slonyregress.logtrigger('_slonyregress', '1', 'k') we could a) build up a similar line in the query in the plpgsql function and do a text comparision b) Do regex matching to extract the 'k' from the arguments c) use the C function like the patch proposes. I dislike (b). I'm not opposed to (a), but comparing just the trigger arguments seems more direct to me, even if it involves a C function to get them -- 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.
- Previous message: [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble
- Next message: [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list