From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | marcin mank <marcin(dot)mank(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu> |
Subject: | Re: [COMMITTERS] pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after |
Date: | 2010-02-15 14:02:35 |
Message-ID: | 201002151502.37654.andres@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Monday 15 February 2010 14:50:03 marcin mank wrote:
> Yes, the issue with initdb failing is unrelated (and I have no problem
> about the fs being unsupported). But fsync still DOES fail on
> directories from the mount.
>
> >> But I would not be that sure that eg. NFS or something like that won`t
> >> complain.
> >
> > It does not.
>
> What if someone mounts a NFS share from a system that does not support
> directory fsync (per buildfarm: unixware, AIX) on Linux? I agree that
> this is asking for trouble, but...
Then nothing. The fsync via nfs or such is a local operation. There is nothing
like a "fsync" command transported - i.e. the fsync controls the local cache
not the remote one...
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-02-15 14:15:40 | Re: [COMMITTERS] pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after |
Previous Message | marcin mank | 2010-02-15 13:50:03 | Re: [COMMITTERS] pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-02-15 14:12:42 | Re: Documentation build issues on Debian/Ubuntu |
Previous Message | marcin mank | 2010-02-15 13:50:03 | Re: [COMMITTERS] pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after |