On Thu, Jan 21, 2010 at 4:27 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > It's a good question if that still makes sense with Hot Standby. Perhaps > we should redefine smart shutdown in standby mode to shut down as soon > as all read-only connections have died.
Okay. Let's work out the details. I guess that the startup process and the walreceiver should wait for all read only backends to exit in smart shutdown case. It's because those backends might be waiting for the record that conflicts with their queries to be replayed. Is this OK? Or we should kill the startup process and the walreceiver on ahead? If my guess is right, we would need to add new PMState to cancel recovery and replication after all read only connections have died. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers