Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint

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-07 12:33:51
Message-ID: 20040207123350.GH2608@filer
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-hackers-win32

I wrote:
> But that someplace else
> could easily be a process forked by the backend in question whose sole
> purpose is to go through the list of files generated by its parent backend
> and fsync() them. The backend can then go about its business and upon
> receipt of the SIGCHLD notify anyone that needs to be notified that the
> fsync()s have completed.

Duh, what am I thinking? Of course, the right answer is to have the
child notify anyone that needs notification that fsync()s are done. No
need for involvement of the parent (i.e., the backend in question)
unless the architecture of PG requires it somehow.

--
Kevin Brown kevin(at)sysexperts(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2004-02-07 14:46:12 Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint
Previous Message Tom Lane 2004-02-07 07:21:37 Re: Make failed in HEAD with make -j

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Bruce Momjian 2004-02-08 01:44:45 Re: [HACKERS] Sync vs. fsync during checkpoint
Previous Message Kevin Brown 2004-02-07 03:55:42 Re: [pgsql-hackers-win32] Sync vs. fsync during checkpoint