[Cl-perec-devel] Special requirements

Leslie P. Polzer leslie.polzer at gmx.net
Thu Aug 21 19:11:01 UTC 2008

> currently each slot change ends up in an sql update. it could be
> optimized to gather slot changes until the transaction is actually
> comitted, but it changes the semantics slightly and there are also
> other lower fruits before that optimization.

Ah, so I need to explicitly wrap all slot writes/uncached reads

Also, is there a perec-idiomatic way to set the pg isolation level?

More information about the cl-perec-devel mailing list