"Tom Lane" <[EMAIL PROTECTED]> writes: > 4. Keep spawning a child, but mark it in the BackendList as known > doomed, and don't count such children when deciding if it's OK to > terminate. The problem with this idea is that such children will > still be connected to shared memory, and we really don't want to > terminate the postmaster before all connections to shmem are gone. > (This objection also applies to #1, now that I think about it.) > > I'm sort of leaning to solution #3, but I wondered if anyone had > a different opinion or a better idea.
A variant on option 4 would be to stop accepting new connections once there are only known-doomed clients left. Ie, behave as if we're shut down already but not actually exit until all the known-doomed clients drain out. I think I agree that option 3 sounds simpler though. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
