From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Moving relation extension locks out of heavyweight lock manager |
Date: | 2017-05-12 03:44:04 |
Message-ID: | 25181.1494560644@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, May 10, 2017 at 8:39 PM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>> ... I'd like to propose to change relation
>> extension lock management so that it works using LWLock instead.
> That's not a good idea because it'll make the code that executes while
> holding that lock noninterruptible.
Is that really a problem? We typically only hold it over one kernel call,
which ought to be noninterruptible anyway. Also, the CheckpointLock is
held for far longer, and we've not heard complaints about that one.
I'm slightly suspicious of the claim that we don't need deadlock
detection. There are places that e.g. touch FSM while holding this
lock. It might be all right but it needs close review, not just an
assertion that it's not a problem.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-05-12 03:50:03 | Re: PG 10 release notes |
Previous Message | Michael Paquier | 2017-05-12 03:35:08 | Re: PG 10 release notes |