Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin.
От | Greg Stark |
---|---|
Тема | Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin. |
Дата | |
Msg-id | 407d949e1001231340n36a2cb9i28cc6693b0f17996@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgsql: In HS, Startup process sets SIGALRM when waiting for buffer pin. (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: pgsql: In HS, Startup process sets SIGALRM when waiting for
buffer pin.
|
Список | pgsql-hackers |
On Sat, Jan 23, 2010 at 8:28 PM, Simon Riggs <simon@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
В списке pgsql-hackers по дате отправления: