From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Din Adrian <adrian(dot)din(at)easynet(dot)ro> |
Cc: | 'Postgresql Performance' <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Tunning postgresql on linux (fedora core 3) |
Date: | 2005-02-03 13:56:50 |
Message-ID: | 42022DA2.3040000@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance pgsql-sql |
Please CC the mailing list as well as replying to me, so that others can
help too.
Din Adrian wrote:
> yes I have read this as well ...
>
> One question about this option:
> fsync = true / false
> a) I have Raid and UPS - it is safe to turn this off ... (' But be
> very aware that any unexpected database shutdown will force you to
> restore the database from your last backup.' - from my last backup if
> the server goes down ??? why ? just at 'any unexpected database
> shutdown' ? ....!!!!!!!!!!!)
Because fsync=true flushes transaction details to disk (the Write Ahead
Log). That way if (say) the power-supply in your server fails you can
check the WAL and compare it to the main database files to make sure
everything is in a known state.
> b) in docs say that after 7.2 seting this to false does'n turn off the
> wall ...!? wich option does?
The docs don't say that, as far as I can see. It doesn't make sense to
turn off the WAL.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2005-02-03 13:59:25 | Re: [postgis-users] Bad query optimizer misestimation because of |
Previous Message | Marinos J. Yannikos | 2005-02-03 13:15:50 | Re: GiST indexes and concurrency (tsearch2) |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Glaesemann | 2005-02-03 14:14:45 | Re: pg primary key bug? |
Previous Message | pginfo | 2005-02-03 13:52:16 | Re: pg primary key bug? |