On Wed, Nov 23, 2011 at 9:09 PM, Steve Singer <[email protected]> wrote:
> So why would a SERIALIZABLE READ ONLY DEFERRED transaction produce fewer > conflicts than a READ COMMITTED transaction? Currently the remote_listener > gets the default isolation level (READ COMMITTED). The setting of READ ONLY DEFERRED as you had it doesn't make sense. DEFERRED only does something if you ask for SERIALIZABLE as well. Marking things READ ONLY makes sense because it could prevent serializable errors in other transactions. As to whether you need SERIALIZABLE, deferred or otherwise in the listener is not for me to say. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
