On Tue, Jun 9, 2015 at 5:21 AM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Fujii Masao wrote: >> Hi, >> >> When the archiver exits, currently reaper() restarts it only while >> the postmaster state is PM_RUN. This is OK in 9.4 or before because >> the archiver could be running on that state. But in 9.5, we can set >> archive_mode to "always" and start the archiver even on the standby. >> So I think that reaper() should restart the archiver even when >> the postmaster state is PM_RECOVERY or PM_HOT_STANDBY with >> some conditions. Patch attached. > > Sounds reasonable, but the patch looks pretty messy.
Thanks for reviewing the patch! > Can't we create > some common function that would be called both here and on ServerLoop? Agreed. So, what about the attached patch? > We also have sigusr1_handler that starts an archiver -- why does that > one use different conditions? Because that code path can be reached only during recovery. So XLogArchivingActive() which indicates whether archiver is allowed to start during normal processing doesn't need to be checked there. OTOH, in the other places where archiver is started up, we can reach there during not only recovery but also normal processing. So the conditions that we need to check are different. Regards, -- Fujii Masao -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
