| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Florian Weimer <fweimer(at)bfk(dot)de> |
| Cc: | 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 18:08:00 |
| Message-ID: | 20070724180800.GC3926@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
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?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-07-24 18:53:14 | Re: tsearch core path, v0.58 |
| Previous Message | Peter Eisentraut | 2007-07-24 16:12:26 | Re: msvc const warnings |