Re: WAL format changes

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: WAL format changes
Дата
Msg-id CA+TgmobG9VWWvLXeK0XOxoWXtza8JTFgSu2eoAtVFucxH6gLBw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: WAL format changes  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: WAL format changes  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Список pgsql-hackers
On Thu, Jun 14, 2012 at 5:58 PM, Andres Freund <andres@2ndquadrant.com> wrote:
>> 1. Use a 64-bit segment number, instead of the log/seg combination. And
>> don't waste the last segment on each logical 4 GB log file. The concept
>> of a "logical log file" is now completely gone. XLogRecPtr is unchanged,
>> but it should now be understood as a plain 64-bit value, just split into
>> two 32-bit integers for historical reasons. On disk, this means that
>> there will be log files ending in FF, those were skipped before.
> Whats the reason for keeping that awkward split now? There aren't that many
> users of xlogid/xcrecoff and many of those would be better served by using
> helper macros.

I wondered that, too.  There may be a good reason for keeping it split
up that way, but we at least oughta think about it a bit.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: Allow WAL information to recover corrupted pg_controldata
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: WAL format changes