| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Summary and Plan for Hot Standby |
| Date: | 2009-11-15 19:29:34 |
| Message-ID: | 1258313374.14054.2552.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2009-11-15 at 20:37 +0200, Heikki Linnakangas wrote:
> Robert Haas wrote:
> > But a
> > query getting canceled because it touches a lot of tables sounds more
> > like a limitation than an outright bug,
>
> It's not that the query might get canceled. It will abort WAL recovery,
> kill all backends, and bring the whole standby down.
Hmm, I think the incredible exploding Hot Standby is overstating this
somewhat. We can improve the error handling for this rare case for which
a simple workaround exists, but it seems like we should punt to phase 2.
You agree there should be two phases?
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-11-15 19:34:06 | Re: ALTER ROLE/DATABASE RESET ALL versus security |
| Previous Message | David E. Wheeler | 2009-11-15 19:25:36 | Re: named parameters in SQL functions |