Re: increasing the default WAL segment size

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: increasing the default WAL segment size
Дата
Msg-id CAB7nPqS63d=0_yKf-6HHPoU=U3J4tksiqC4Ve-V=u5djpdX5xA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: increasing the default WAL segment size  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: increasing the default WAL segment size  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
On Fri, Aug 26, 2016 at 12:54 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> On Fri, Aug 26, 2016 at 9:04 AM, Michael Paquier
> <michael.paquier@gmail.com> wrote:
>> On Fri, Aug 26, 2016 at 12:25 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>>> If we change the default to 64MB, then I think it won't allow to use
>>> old databases as-is because we store it in pg_control (I think one
>>> will get below error [1] for old databases, if we just change default
>>> and don't do anything else).  Do you have way to address it or you
>>> think it is okay?
>>
>> Those would still be able to work with ./configure
>> --with-wal-segsize=16, so that's not really an issue.
>>
>
> Right, but do we need suggest users to do so?  The question/point was
> if we deliver server with default value as 64MB, then it won't allow
> to start old database.

Right, pg_upgrade could be made smarter by enforcing a conversion with
a dedicated option: we could get away by filling the existing segments
with zeros and add an XLOG switch record at the end of each segments
formerly at 16MB converted to 64MB. That would still be better than
converting each page LSN :(
-- 
Michael



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

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Re: Renaming of pg_xlog and pg_clog
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: Showing parallel status in \df+