Re: XLogInsert

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: XLogInsert
Дата
Msg-id
24638.1250700547@sss.pgh.pa.us
Ответ на
XLogInsert (Jeff Janes)
Список
Дерево обсуждения
XLogInsert Jeff Janes <jeff.janes@gmail.com>
Re: XLogInsert Tom Lane <tgl@sss.pgh.pa.us>
Re: XLogInsert Jeff Janes <jeff.janes@gmail.com>
Re: XLogInsert Jaime Casanova <jcasanov@systemguards.com.ec>
Re: XLogInsert Tom Lane <tgl@sss.pgh.pa.us>
Re: XLogInsert Jaime Casanova <jcasanov@systemguards.com.ec>
Re: XLogInsert Alvaro Herrera <alvherre@commandprompt.com>
Re: XLogInsert Jaime Casanova <jcasanov@systemguards.com.ec>
Re: XLogInsert Greg Smith <greg@2ndquadrant.com>
Re: XLogInsert Gurjeet Singh <singh.gurjeet@gmail.com>
Re: XLogInsert Andres Freund <andres@anarazel.de>
Re: XLogInsert Greg Smith <greg@2ndquadrant.com>
Patch LWlocks instrumentation Pierre Frédéric Caillaud<lists@peufeu.com>
Re: Patch LWlocks instrumentation Jeff Janes <jeff.janes@gmail.com>
Re: Patch LWlocks instrumentation Pierre Frédéric Caillaud<lists@peufeu.com>
Jeff Janes  writes:
> If I read the code correctly, the only thing that is irrevocable is
> that it writes into
> rdt->next, and if it saved an old copy of rdt first, then it could
> revoke the changes just
> by doing rdt_old->next=NULL.  If that were done, then I think this
> code could be
> moved out of the section holding the WALInsertLock.

Hmm, I recall that the changes are ... or were ... more complex.
The tricky case I think is where we have to go back and redo the
block-backup decisions after discovering that the checkpoint REDO
pointer has just moved.

If you can get the work out of the WALInsertLock section for just a
few more instructions, it would definitely be worth doing.
		regards, tom lane

В списке pgsql-hackers по дате отправления
От: Alvaro Herrera
Дата:
От: Tom Lane
Дата:
FAQ