Re: WAL format

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: WAL format
Дата
Msg-id
23971.1260217709@sss.pgh.pa.us
Ответ на
WAL format (Heikki Linnakangas)
Список
Дерево обсуждения
WAL format Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: WAL format Simon Riggs <simon@2ndQuadrant.com>
Re: WAL format Fujii Masao <masao.fujii@gmail.com>
Re: WAL format Alvaro Herrera <alvherre@commandprompt.com>
Re: WAL format Tom Lane <tgl@sss.pgh.pa.us>
Re: WAL format Greg Stark <gsstark@mit.edu>
Re: WAL format Tom Lane <tgl@sss.pgh.pa.us>
Re: WAL format Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: WAL format "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: WAL format Tom Lane <tgl@sss.pgh.pa.us>
Re: WAL format Andres Freund <andres@anarazel.de>
Re: WAL format Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Heikki Linnakangas  writes:
> In particular I wonder why we bother with the page headers. A much
> simpler format would be:

> - get rid of page headers, except for the header at the beginning of
> each WAL segment
> - get rid of continuation records
> - at the end of WAL segment, when there's not enough space to write the
> next WAL record, always write an XLOG SWITCH record to fill the rest of
> the segment.

What do you do with a WAL record that doesn't fit in a segment?  (They
do exist.)  I don't think you can eliminate continuation records.
You could maybe use them only at segment boundaries but I doubt that
makes things any simpler than they are now.
		regards, tom lane

В списке pgsql-hackers по дате отправления
От: Alvaro Herrera
Дата:
Сообщение: Re: WAL format
От: Tom Lane
Дата:
Сообщение: Re: Build sizes vs docs
FAQ