| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reduce ProcArrayLock contention |
| Date: | 2015-06-30 06:36:55 |
| Message-ID: | CANP8+jKpLnzfrnwSv1GgSXJmbqGdtojRADFa+NVrBfg4BUPumA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30 June 2015 at 07:30, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Sure and I think we might want to try something similar even
> for XLogFlush where we use LWLockAcquireOrWait for
> WALWriteLock, not sure how it will workout in that case as
> I/O is involved, but I think it is worth trying.
>
+1
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2015-06-30 06:40:04 | Re: drop/truncate table sucks for large values of shared buffers |
| Previous Message | Amit Kapila | 2015-06-30 06:34:57 | Re: drop/truncate table sucks for large values of shared buffers |