Re: Postgres 8.3 archive_command

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Postgres 8.3 archive_command
Дата
Msg-id 13095.1195666936@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Postgres 8.3 archive_command  (Simon Riggs <simon@2ndquadrant.com>)
Ответы Re: Postgres 8.3 archive_command  (Greg Smith <gsmith@gregsmith.com>)
Re: Postgres 8.3 archive_command  ("Zeugswetter Andreas ADI SD" <Andreas.Zeugswetter@s-itsolutions.at>)
Список pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> On Wed, 2007-11-21 at 18:16 +0100, Zeugswetter Andreas ADI SD wrote:
>> Maybe it is time for making WAL segment size
>> changeable in the conf with a clean shutdown.

> I think its too late in the release cycle to fully consider all the
> implications of that. 16MB is hardcoded in lots of places.

Starting with the WAL file names.  You couldn't even find the last
checkpoint record if this were changed between shutdown and restart;
you'd very likely go looking under the wrong filename, and even if
you hit on an existent filename you'd be looking at the wrong offset
within it.

I don't think that should even be a TODO item --- it seems far more
likely to provide a foot-gun than useful capability.

Whether 16MB is still a reasonable default segment size is worth
questioning, though I don't think that increasing it is an open-and-shut
proposition.  Larger segments mean more overhead in configurations that
force frequent segment switches, for instance.
        regards, tom lane


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

Предыдущее
От: Hannes Eder
Дата:
Сообщение: Re: random dataset generator for SKYLINE operator
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: Postgres 8.3 archive_command