From: Kevin Brown <kevin@sysexperts.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint
Date: Tue, 3 Feb 2004 02:38:42 -0800
Message-ID: <20040203103842.GD2608@filer> (raw)
In-Reply-To: <20040203103605.GC2608@filer>
References: <16010.1075485076@sss.pgh.pa.us>
<200402011333.i11DXmp29214@candle.pha.pa.us>
<20040203103605.GC2608@filer>
Some Moron at sysexperts.com wrote:
> At checkpoint time, for each backend list, the bgwriter grabs a write
> lock on the list, copies it into its own memory space, truncates the
> list, and then releases the read lock.
Sigh. I meant to say that it then releases the *write* lock.
--
Kevin Brown kevin@sysexperts.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: kevin@sysexperts.com
Subject: Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint
In-Reply-To: <20040203103842.GD2608@filer>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox