| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hot Standby remaining issues |
| Date: | 2009-12-02 11:00:14 |
| Message-ID: | 1259751614.13774.21183.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2009-12-02 at 12:49 +0200, Heikki Linnakangas wrote:
> If a read-only transaction holds a lot of locks, consuming so much
> lock space that there's none left for the startup process to hold the
> lock it wants, it will abort and bring down postmaster. The patch
> attempts to kill any conflicting lockers, but those are handled fine
> already (if there's any conflicting locks, LockAcquire will return
> LOCKACQUIRE_NOT_AVAIL anyway). The problem is with non-conflicting
> locks using up the lock space.
Oh dear, another "nuke 'em all from orbit" scenario. Will do.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurent Laborde | 2009-12-02 11:13:35 | Re: Cost of sort/order by not estimated by the query planner |
| Previous Message | Heikki Linnakangas | 2009-12-02 10:49:37 | Re: Hot Standby remaining issues |