On 08/10/2013 04:26 AM, Greg Stark wrote: > On Sat, Aug 10, 2013 at 5:30 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> Any other client would behave the same >> if it were killed while waiting for some backend query. So the right >> fix would involve figuring out a way for the backend to kill itself >> if the client connection goes away while it's waiting.
I've been waiting forever to have something we can justifiably call the "loner suicide patch". ;-) > I'm surprised this is the first time we're hearing people complain > about this. I know I've seen similar behaviour from Mysql and thought > to myself that represented pretty poor behaviour and assumed Postgres > did better. No, it's been a chronic issue since we got SMP support, pretty much forever. Why do you think we have pg_terminate_backend()? The problem, as explored downthread, is that there's no clear way to fix this. It's a problem which goes pretty far beyond PostgreSQL; you can experience the same issue on Apache with stuck downloads. Our advantage over MySQL is that the idle process isn't likely to crash anything ... -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
