From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Grant Finnemore <gaf(at)ucs(dot)co(dot)za>, pgsql-hackers(at)postgresql(dot)org, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Subject: | Re: SET FSYNC command? |
Date: | 2000-05-31 10:43:54 |
Message-ID: | Pine.GSO.4.02A.10005311237540.698-100000@Gepard.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 31 May 2000, Tom Lane wrote:
> > If SHOW PG_OPTIONS; is executed, one of the lines is
> > o NOTICE: nofsync=0
> > now, SET PG_OPTIONS TO 'nofsync=1';
> > SHOW PG_OPTIONS;
> > o NOTICE: nofsync=1
> The syntax is unnecessarily obscure and arse-backwards :-(.
No kidding.
Actually, since yesterday you can disable fsync in a multitude of ways:
postmaster -F
postmaster -o '-F'
postmaster --enable-fsync=off
SET ENABLE_FSYNC TO OFF;
but feel free to not care because after all ...
> Once the WAL revisions are done the whole issue will go away anyway,
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2000-05-31 13:47:45 | Re: SET FSYNC command? |
Previous Message | Zeugswetter Andreas SB | 2000-05-31 07:28:51 | AW: Applying TOAST to CURRENT |