On Fri, Jan 20, 2012 at 10:30 PM, Heikki Linnakangas
> I spent some time cleaning this up. Details below, but here are the
> * Reverted the removal of wal_writer_delay
> * Removed heuristic on big flushes
No contested viewpoints on anything there.
> * Doesn't rely on WAL writer. Any process can act as the "leader" now.
> * Uses PGSemaphoreLock/Unlock instead of latches
Thanks for producing an alternate version, it will allow us to comment
on various approaches.
There is much yet to discuss so please don't think about committing
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
In response to
pgsql-hackers by date
|Next:||From: Pavan Deolasee||Date: 2012-01-25 03:53:50|
|Subject: Re: some longer, larger pgbench tests with various
|Previous:||From: Bruce Momjian||Date: 2012-01-25 03:47:35|
|Subject: Re: pg_upgrade with plpython is broken|