Re: [HACKERS] Replication/backup defaults
От | Simon Riggs |
---|---|
Тема | Re: [HACKERS] Replication/backup defaults |
Дата | |
Msg-id | CANP8+jJe_WGVUpdQy=o5bSFborY-YOdbkjiPPUK_Kyk5gLC8hA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Replication/backup defaults (Simon Riggs <simon@2ndquadrant.com>) |
Список | pgsql-hackers |
On 2 January 2017 at 09:48, Simon Riggs <simon@2ndquadrant.com> wrote: > I'm willing to assist in a project to allow changing wal_level online > in this release. Please let's follow that path. wal_level looks like one of the easier ones to change without a server restart There are actions to take in either direction, up or down. My initial thoughts on the pseudocode would be... reset wal_level so all new transactions see that value /* actions after setting new value */ if (old_wal_level < new_wal_level) /* going up */ get list of running transactions (perhaps only those using no-WAL-opt) else /* coming down */ {if (old_wal_level == logical) disconnect logical replication and disallow logical slotsif (new_wal_level == minimal) disconnectstreaming replication and disallow physical slots } wait for a checkpoint (fast checkpoint if no other transactions actions active) if (list) wait for list of running xacts to complete wait for a checkpoint (fast checkpoint if no other transactions actions active) XLogReportParameters() So it looks easier to go up than down, which is good since that is the important direction. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: