Robert Haas <robertmhaas@xxxxxxxxx> writes: > AIUI, whenever the connection pooler switches to serving a new client, > it tells the PG backend to DISCARD ALL. But why couldn't we just > implement this same logic internally? IOW, when a client disconnects, > instead of having the backend exit immediately, have it perform the > equivalent of DISCARD ALL and then stick around for a minute or two > and, if a new connection request arrives within that time, have the > old backend handle the new connection... See previous discussions. IIRC, there are two killer points: 1. There is no (portable) way to pass the connection from the postmaster to another pre-existing process. 2. You'd have to track which database, and probably which user, each such backend had been launched for; reconnecting a backend to a new database is probably impractical and would certainly invalidate all the caching. Overall it looked like way too much effort for way too little gain. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
