Re: LWLocks in DSM memory - Mailing list pgsql-hackers

From Andres Freund
Subject Re: LWLocks in DSM memory
Date
Msg-id 20160816210330.d73qq6ffq2edi4jv@alap3.anarazel.de
Whole thread Raw
In response to Re: LWLocks in DSM memory  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: LWLocks in DSM memory  (Robert Haas <robertmhaas@gmail.com>)
Re: LWLocks in DSM memory  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2016-08-15 18:15:23 -0400, Robert Haas wrote:
> On Thu, Aug 11, 2016 at 2:19 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> > Therefore, I plan to commit this patch, removing the #include
> > <stddef.h> unless someone convinces me we need it, shortly after
> > development for v10 opens, unless there are objections before then.
> 
> Hearing no objections, done.

I'd have objected, if I hadn't been on vacation.  While I intuitively
*do* think that the increased wait-list overhead won't be relevant, I
also know that my intuition has frequently been wrong around the lwlock
code.  This needs some benchmarks on a 4+ socket machine,
first. Something exercising the slow path obviously. E.g. a pgbench with
a small number of writers, and a large number of writers.

Regards,

Andres



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] C++ port of Postgres
Next
From: Piotr Stefaniak
Date:
Subject: Re: [GENERAL] C++ port of Postgres