Re: checkpoint_timout with no WAL activity
От | amul sul |
---|---|
Тема | Re: checkpoint_timout with no WAL activity |
Дата | |
Msg-id | CAAJ_b94+BX5YYPVzGy5DG_nLXBHFtQutbb6enM+sjeqOYoCbqg@mail.gmail.com обсуждение исходный текст |
Ответ на | checkpoint_timout with no WAL activity (Tom DalPozzo <t.dalpozzo@gmail.com>) |
Ответы |
Re: checkpoint_timout with no WAL activity
Re: checkpoint_timout with no WAL activity |
Список | pgsql-general |
On Mon, Nov 7, 2016 at 4:20 PM, Tom DalPozzo <t.dalpozzo@gmail.com> wrote: > Hi, > I have: > checkpoint_timeout = 2min > wal_level = archive > archive_mode=on > archive_timeout = 30 > > With NO dbase activity, I see the WAL being modified every 2min (and, > consequently, one WAL file archived every 2min too ). > > Is it right? I read: "If no WAL has been written since the previous > checkpoint, new checkpoints will be skipped even if checkpoint_timeout has > passed." I guess archive_timeout forcing to switch new WAL file, see this : https://www.postgresql.org/docs/devel/static/runtime-config-wal.html#GUC-ARCHIVE-TIMEOUT Regards, Amul
В списке pgsql-general по дате отправления: