Hi!
I ended up with the same error as Jan Wieck wrote about in this post
(permission denied for sequence sl_action_seq):
http://gborg.postgresql.org/pipermail/slony1-general/2007-February/005849.html
<http://gborg.postgresql.org/pipermail/slony1-general/2007-February/005849.html>
In my app is using the same technique as described in the post above; a row is
inserted in a parent table and a couple of rows are inserted in a childtable
with a foreign key based on lastval. This is obviosouly not a good solution.
I've not told the application to access this sequence in any way and it worked
fine until I installed and turned on slony. The sql statement that reports the
error is the only piece where lastval is used.
Just for the sake of clarity, its recommended to use currval() instead of
lastval(). Or are there an other methods that I should consider to find out the
last inserted id?
Cheers!
// John
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
