From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Anuradha Ratnaweera <anuradha(at)gnu(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oliver Vecernik <vecernik(at)aon(dot)at>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Re: Re: disable wal |
Date: | 2001-05-02 20:07:51 |
Message-ID: | 200105022007.f42K7pw25558@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
>
> I understand that that WAL is an integral part of 7.1 and "disabling" is
> not possible. I also don't want to switch back to 7.0 becuse I _DO_ need
> the new features.
>
> If I don't care for reliability (for reasons I outlined earlier in this
> thread), are there other parameters I can set to optimize for speed, such
> as wal_sync_method? I already have turned off fsync and log_connections. I
> can't turn on silent mode, because this machine is used for all testing
> purposes and messages are useful.
>
> Also, it is possible to avoid postgresql from trying to force the OS to
> write data to the disk, so that WAL writes will be in disk cache for some
> time?
Yes, as Tom said, you can use postgres -F flag to disable fsync writes,
even with WAL in 7.1.
>
> Anuradha
>
> On Mon, 30 Apr 2001, Tom Lane wrote:
>
> > There is no way to "disable WAL". However, you might try running with
> > fsync turned off if you don't care about data integrity.
> >
> > regards, tom lane
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Jaume Teixi | 2001-05-03 15:46:33 | best plase to put custom .so modules |
Previous Message | Tom Lane | 2001-05-02 14:53:59 | Re: Restoring a pg_dump fails with |