On Wed, Mar 14, 2012 at 3:29 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> I think my analysis is pretty much a re-wording of yours, but I'd
> emphasize that getting the WALWriteLock is bad not just because they
> fight over the lock, but because someone else (probably background wal
> writer) is camping out on the lock while doing an fsync.
Yeah, good point.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2012-03-14 20:56:37|
|Subject: Re: patch for parallel pg_dump|
|Previous:||From: email@example.com||Date: 2012-03-14 20:53:45|
|Subject: Re: Faster compression, again|