Re: Async Commit, v21 (now: v22)
От
Tom Lane
Тема
Re: Async Commit, v21 (now: v22)
Дата
Msg-id
15643.1185308707@sss.pgh.pa.us
Ответ на
Re: Async Commit, v21 (now: v22) (Jim C. Nasby)
Список
Дерево обсуждения
Async Commit, v21 "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 Bruce Momjian <bruce@momjian.us>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Bruce Momjian <bruce@momjian.us>
Re: Async Commit, v21 (now: v22) Peter Eisentraut <peter_e@gmx.net>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Tom Lane <tgl@sss.pgh.pa.us>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Alvaro Herrera <alvherre@commandprompt.com>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Tom Lane <tgl@sss.pgh.pa.us>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Tom Lane <tgl@sss.pgh.pa.us>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Gregory Stark <stark@enterprisedb.com>
Re: Async Commit, v21 (now: v22) Tom Lane <tgl@sss.pgh.pa.us>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Heikki Linnakangas <heikki@enterprisedb.com>
Re: Async Commit, v21 (now: v22) Gregory Stark <stark@enterprisedb.com>
Re: Async Commit, v21 (now: v22) Tom Lane <tgl@sss.pgh.pa.us>
Re: Async Commit, v21 (now: v22) Greg Smith <gsmith@gregsmith.com>
Re: Async Commit, v21 (now: v22) Heikki Linnakangas <heikki@enterprisedb.com>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Alvaro Herrera <alvherre@commandprompt.com>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Alvaro Herrera <alvherre@commandprompt.com>
Re: Async Commit, v21 (now: v22) Tom Lane <tgl@sss.pgh.pa.us>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Tom Lane <tgl@sss.pgh.pa.us>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Florian Weimer <fweimer@bfk.de>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Florian Weimer <fweimer@bfk.de>
Re: Async Commit, v21 (now: v22) Alvaro Herrera <alvherre@commandprompt.com>
Re: Async Commit, v21 (now: v22) "Jim C. Nasby" <decibel@decibel.org>
Re: Async Commit, v21 (now: v22) Tom Lane <tgl@sss.pgh.pa.us>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Tom Lane <tgl@sss.pgh.pa.us>
Re: Async Commit, v21 (now: v22) "Simon Riggs" <simon@2ndquadrant.com>
Re: Async Commit, v21 (now: v22) Gregory Stark <stark@enterprisedb.com>
"Jim C. Nasby" writes: > On Tue, Jul 24, 2007 at 02:08:00PM -0400, Alvaro Herrera wrote: >> 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... How do you arrive at that conclusion? The point of the async commit patch is that transactions might be lost, as in not really committed, but there can be no database corruption. Otherwise we'd never consider making it a userset config setting. regards, tom lane
В списке pgsql-patches по дате отправления