| 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 |
| Subject: | Re: Recovery control functions |
| Date: | 2011-01-14 12:54:43 |
| Message-ID: | 1295009683.12442.89.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2011-01-14 at 14:27 +0200, Heikki Linnakangas wrote:
> > Trouble is, if you wait on Latch X and other processes send wakeup
> > assuming you were waiting on Latch Y, then this will erroneously wake
> > you up.
>
> The signal will wake up the process, but WaitLatch will quickly go back
> to sleep if it wasn't for the latch we're waiting for. I don't think
> that causes any meaningful performance issues.
Neither does polling.
> So that's all handled within the latch code.
I'll adjust the comment.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-01-14 13:05:05 | Re: Allowing multiple concurrent base backups |
| Previous Message | Heikki Linnakangas | 2011-01-14 12:30:35 | Re: [COMMITTERS] pgsql: Exit from base backups when shutdown is requested |