| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reducing ClogControlLock contention |
| Date: | 2015-07-02 18:17:16 |
| Message-ID: | CA+TgmoYjpNKdHDFUtJLAMna-O5LGuTDnanHFAOT5=hN_VAuW2Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 1, 2015 at 6:21 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2015-07-01 11:19:40 +0100, Simon Riggs wrote:
>> What "tricks" are being used??
>>
>> Please explain why taking 2 locks is bad here, yet works fine elsewhere.
>
> I didn't say anything about 'bad'. It's more complicated than one
> lock. Suddenly you have to care about lock ordering and such. The
> algorithms for ensuring correctness gets more complicated.
Taking two locks might also be more expensive than just taking one. I
suppose benchmarking will reveal whether there is an issue there.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robbie Harwood | 2015-07-02 18:22:13 | [PATCH v1] GSSAPI encryption support |
| Previous Message | Heikki Linnakangas | 2015-07-02 18:14:37 | Re: Memory leak fixes for pg_dump, pg_dumpall, initdb and pg_upgrade |