| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Greg Stark <gsstark(at)mit(dot)edu> |
| Subject: | Re: Hot Standby and deadlock detection |
| Date: | 2010-02-01 17:05:19 |
| Message-ID: | 1265043919.13782.12556.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2010-02-01 at 17:50 +0200, Heikki Linnakangas wrote:
> Umm, so why not run the deadlock check immediately in
> max_standby_delay=-1 case as well? Why is that case handled differently
> from max_standby_delay>0 case?
Done, tested, working.
Will commit tomorrow if no further questions or comments.
--
Simon Riggs www.2ndQuadrant.com
| Attachment | Content-Type | Size |
|---|---|---|
| startup_deadlock_check.v2.patch | text/x-patch | 10.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-01 17:12:09 | Re: pgsql: Augment EXPLAIN output with more details on Hash nodes. |
| Previous Message | Robert Haas | 2010-02-01 17:01:55 | Re: pgsql: Augment EXPLAIN output with more details on Hash nodes. |