Fri Feb 20 19:47:43 PST 2009
- Previous message: [Slony1-general] Firing a trigger on a slony replicated table...
- Next message: [Slony1-general] slony rep error on start up: Slony-I: setAddTable_int():
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, 21 Feb 2009 12:26:32 +1300 Steve Holdoway <steve at greengecko.co.nz> wrote: with thanks offlist pointing me to the ENABLE ALWAYS TRIGGER , I'm moving slowly forwards. I'm now getting slony errors about violating unique keys when the insert statement to add to the table outside the replication - same database, separate schema. If I log in to the database from the command line, and copy/paste the statement posted as violating the unique key, it works fine. Is there a decent writeup anywhere of that the environmental differences that I need to take into account to get this software working? In this case, I'm using an EXECUTE 'INSERT INTO...' syntax, as it's a dynamic string. If it's more efficient ( and available in pl/pgsql ), then I could use prepared statements instead... Cheers, Steve -- Steve Holdoway <steve at greengecko.co.nz>
- Previous message: [Slony1-general] Firing a trigger on a slony replicated table...
- Next message: [Slony1-general] slony rep error on start up: Slony-I: setAddTable_int():
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list