Re: comment for "fast promote"
От | Fujii Masao |
---|---|
Тема | Re: comment for "fast promote" |
Дата | |
Msg-id | CAHGQGwEBUvgcx8X+Z0Hh+VdwYcJ8KCuRuLt1jSsxeLxPcX=0_w@mail.gmail.com обсуждение исходный текст |
Ответ на | comment for "fast promote" (Tomonari Katsumata <katsumata.tomonari@po.ntts.co.jp>) |
Ответы |
Re: comment for "fast promote"
|
Список | pgsql-hackers |
On Thu, Jul 25, 2013 at 5:33 PM, Tomonari Katsumata <katsumata.tomonari@po.ntts.co.jp> wrote: > Hi, > > Now I'm seeing xlog.c in 93_stable for studying "fast promote", > and I have a question. > > I think it has an extra unlink command for "promote" file. > (on 9937 line) > ------- > 9934 if (stat(FAST_PROMOTE_SIGNAL_FILE, &stat_buf) == 0) > 9935 { > 9936 unlink(FAST_PROMOTE_SIGNAL_FILE); > 9937 unlink(PROMOTE_SIGNAL_FILE); > 9938 fast_promote = true; > 9939 } > ------- > > Is this command necesary ? Yes, it prevents PROMOTE_SIGNAL_FILE from remaining even if both promote files exist. One question is that: we really still need to support normal promote? pg_ctl promote provides only way to do fast promotion. If we want to do normal promotion, we need to create PROMOTE_SIGNAL_FILE and send the SIGUSR1 signal to postmaster by hand. This seems messy. I think that we should remove normal promotion at all, or change pg_ctl promote so that provides also the way to do normal promotion. Regards, -- Fujii Masao
В списке pgsql-hackers по дате отправления: