| From: | Kevin Brown <kevin(at)sysexperts(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint |
| Date: | 2004-02-03 10:38:42 |
| Message-ID: | 20040203103842.GD2608@filer |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 |
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(at)sysexperts(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Brown | 2004-02-03 10:57:46 | Re: COPY from question |
| Previous Message | Kevin Brown | 2004-02-03 10:36:05 | Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Kuhmonen | 2004-02-03 12:48:23 | Re: pg_config.h on interix |
| Previous Message | Kevin Brown | 2004-02-03 10:36:05 | Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint |