| From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
|---|---|
| To: | Florian Weimer <fweimer(at)bfk(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Gregory Stark <stark(at)enterprisedb(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Async Commit, v21 (now: v22) |
| Date: | 2007-07-24 20:11:43 |
| Message-ID: | 20070724201142.GV39272@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Tue, Jul 24, 2007 at 02:08:00PM -0400, Alvaro Herrera wrote:
> Florian Weimer wrote:
>
> > I think fsync=off also endagers metadata, while synchronous_commit=off
> > should be perfectly safe as far as the metadata is concerned.
> > Wouldn't this be worth mentioning as well?
>
> Is it true that a transaction is turned into sync commit as soon as it
> writes on a system catalog? Is it desirable to make it so?
If we don't do that then regular users have the ability to put the
catalog (and by extension everything else) at risk... I think we need
that, though it would be nice if it wasn't an issue for temporary
objects (but I can't see any way to accomplish that).
--
Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-07-24 20:25:07 | Re: Async Commit, v21 (now: v22) |
| Previous Message | Andrew Dunstan | 2007-07-24 19:45:43 | Re: msvc and vista fun |