I've spoken to people on the torque user mailing list and tried merlin's suggestion below (which looked like it should work - but unfortunately did not prevent the problem). >From working through things with the torque list, it seems to be the case that postgresql is behaving differently because it is not attached to a terminal (this has caused problems for others on that list with sqlite and mysql). Can anyone confirm/refute this? And if it is the case, is there something that I can do about it? thanks again. Dan On Mon, 2009-12-07 at 18:33 -0500, Merlin Moncure wrote: > If it turns out you need to have a lock with a 'longer than > transaction' duration, maybe advisory locks are a good fit. > > merlin > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
