From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [pgsql-hackers-win32] fsync with sync, and Win32 unlink |
Date: | 2004-03-11 18:46:41 |
Message-ID: | 21654.1079030801@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> I've seen some pretty severe damage caused by calling sync(2) on a loaded
> system. The system in question was in the process of copying data to an NFS
> mounted archival site. When the sync hit basically everything stopped until
> the buffered network writes could be synced. The live database was basically
> frozen for a few seconds and the web site nearly crashed. The sysadmin had to
> send out a notice asking everybody to refrain from using sync until the
> archival process had completed.
This seems, um, hard to believe. Did he shut down the standard syncer
daemon? I have never seen a Unix system that would allow more than
thirty seconds' worth of unwritten buffers to accumulate, and would not
care to use one if it existed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2004-03-11 18:50:01 | Re: client side syntax error localisation for psql (v1) |
Previous Message | Tom Lane | 2004-03-11 18:42:32 | Re: creating index on changed field type |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2004-03-11 19:01:05 | Re: [pgsql-hackers-win32] fsync with sync, and Win32 unlink |
Previous Message | Barry Lind | 2004-03-11 18:10:21 | Thanks for the great work on the Win32 port |