On Sat, Jan 23, 2010 at 8:28 PM, Simon Riggs <si...@2ndquadrant.com> wrote: > What is your proposed way of handling buffer pin deadlocks? That will be > acceptable and working to some extent in the next week? > > Wait forever isn't always a good idea, anymore, if it ever was.
I've never said it was always a good idea. But killing correctly running queries isn't always a good idea either. I'm interested in using HS for running read-only replicas for load balancing. It would pretty sad if queries dispatched to a read-only replica received a spurious unpredictable errors for reasons the application programmer cannot control. I'll look at the buffer pin deadlock problem again, but I didn't realize the situation was so dire. And what were the downsides of the "stop gap"? -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
