| From: | Hiroyuki Yamada <yamada(at)kokolink(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: An example of bugs for Hot Standby |
| Date: | 2009-12-18 11:13:24 |
| Message-ID: | 200912181113.AA00178@silver.kokolink.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>This way we only cancel direct deadlocks.
>
>It doesn't solve general problem of buffer waits, but they may be
>solvable by different mechanism.
>
Following question may be redundant. Just a confirmation.
Deadlock example is catstrophic while it's rather a rare event.
On the other hand, LockBufferForCleanup() can cause another
problem.
* One idle pin-holder backend can freeze startup process().
This problem is not catstrophic, but it seems a similar problem
which StandbyAcquireAccessExclusiveLock() tries to avoid.
...Is this the problem you call "general problem" above ?
regards,
--
Hiroyuki YAMADA
Kokolink Corporation
yamada(at)kokolink(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-12-18 12:49:19 | Re: PATCH: Add hstore_to_json() |
| Previous Message | Cédric Villemain | 2009-12-18 10:23:09 | Re: Buffer statistics for pg_stat_statements |