RequestAddinLWLocks(int n)

From: Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: RequestAddinLWLocks(int n)
Date: 2015-07-31 15:56:20
Message-ID: 55BB9AA4.6090101@redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Currently

Max(lock_addin_request, NUM_USER_DEFINED_LWLOCKS);

LWLock's are added during startup for extensions.

However, this presents a problem if an extension doesn't specify the
correct number of LWLock's needed, if the total number is <= 4.

The attached patch requires extensions to specify the correct number of
LWLock's needed. This change will break extensions that specifies an
incorrect number, but makes it easier to debug which extension which is
at fault.

Probably too big a change though. Maybe a patch against xfunc.sgml is
better ?

Best regards,
Jesper

Attachment Content-Type Size
lwlock.patch text/x-patch 1012 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2015-07-31 16:48:28 Re: LWLock deadlock and gdb advice
Previous Message Simon Riggs 2015-07-31 15:14:45 Re: brin index vacuum versus transaction snapshots