On Fri, 2005-04-29 at 16:50 +0200, Kjetil Kjernsmo wrote: > I guess it could be that the use we make of Apache::Session is flawed, > that we should call an update somewhere, but it works (apparently) with > the other data stores. It feels like there is something in the > direction of transactions but I can't figure out what... Or, if it > could be somebody else's bug, relieve me of the feeling of being > stupid... :-)
It is possible that the FOR UPDATE is spurious. It signals to the database system that this transaction intends to write that row. With PostgreSQL's MVCC transaction isolation system, it's probably not necessary and may be causing problems. Note that I handed the pumpkin over to Casey West several months ago. Any issues should be forwarded thereto. -jwb
