On Thu, Jul 28, 2011 at 11:10 AM, Hannu Krosing <ha...@2ndquadrant.com> wrote: > My main point was, that we already do synchronization when writing wal, > why not piggyback on this to also update latest snapshot .
Well, one problem is that it would break sync rep. Another problem is that pretty much the last thing I want to do is push more work under WALInsertLock. Based on the testing I've done so far, it seems like WALInsertLock, ProcArrayLock, and CLogControlLock are the main bottlenecks here. I'm focusing on ProcArrayLock and CLogControlLock right now, but I am pretty well convinced that WALInsertLock is going to be the hardest nut to crack, so putting anything more under there seems like it's going in the wrong direction. IMHO, anyway. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers