Alvaro Herrera wrote: > Excerpts from Tom Lane's message of lun nov 15 02:41:40 -0300 2010: > > > I believe also that there are probably race conditions in several of > > the steps you listed; in particular there is certainly a risk involved > > in changing the database-we-advertise-being-connected-to versus a > > concurrent DROP DATABASE. Maybe that's easily soluble, but I'm not sure > > about it. > > Perhaps it would help to first disconnect from the original database and > not reconnect to any one in particular, i.e. stay in a state like the > autovac launcher is in. Then cleanup as per Robert's list, then switch > to a valid database ID.
One question is whether we keep our caches in the hope we will continue with the same database, or clear our caches so we don't have to incur the overhead of clearing them when we connect a new session. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
