Re: why postgresql over other RDBMS
От
A.M.
Тема
Re: why postgresql over other RDBMS
Дата
Msg-id
377ABCF8-A407-47F3-88A8-F24FCD79D9B6@themactionfaction.com
Ответ на
Re: why postgresql over other RDBMS (Chris Browne)
Список
Дерево обсуждения
Re: why postgresql over other RDBMS Wiebe Cazemier <halfgaar@gmx.net>
Re: why postgresql over other RDBMS "A.M." <agentm@themactionfaction.com>
Re: why postgresql over other RDBMS Alvaro Herrera <alvherre@commandprompt.com>
Re: why postgresql over other RDBMS Naz Gassiep <naz@mira.net>
Re: why postgresql over other RDBMS "A.M." <agentm@themactionfaction.com>
Re: why postgresql over other RDBMS "Alexander Staubo" <alex@purefiction.net>
Re: why postgresql over other RDBMS PFC <lists@peufeu.com>
Re: why postgresql over other RDBMS "A.M." <agentm@themactionfaction.com>
Re: why postgresql over other RDBMS Andrew Sullivan <ajs@crankycanuck.ca>
Re: why postgresql over other RDBMS "A.M." <agentm@themactionfaction.com>
On May 24, 2007, at 18:21 , Chris Browne wrote: > > Jan Wieck had a proposal to a similar effect, namely to give some way > to get one connection to duplicate the state of another one. > > This would permit doing a neat parallel decomposition of pg_dump: you > could do a 4-way parallelization of it that would function something > like the following: > > - connection 1 opens, establishes the usual serialized mode > transaction > > - connection 1 dumps the table metadata into one or more files in a > specified directory > > - then it forks 3 more connections, and seeds them with the same > serialized mode state > > - it then goes thru and can dump 4 tables concurrently at a time, > one apiece to a file in the directory. > > This could considerably improve speed of dumps, possibly of restores, > too. > > Note that this isn't related to subtransactions... Well, I was thinking that since transactions are now serializable, it should be possible to move the state between existing open transactions. -M
В списке pgsql-general по дате отправления
От: Michael Nolan
Дата: