Postgres Pro
Downloads
Home   >   mailing lists

Re: global barrier & atomics in signal handlers (Re: Atomicoperations within spinlocks) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: global barrier & atomics in signal handlers (Re: Atomicoperations within spinlocks)
Date
Msg-id CA+TgmobQP3_9VOra+Bk08BZg+fyHB8hJT99rDOYQu7-S=Dfusg@mail.gmail.com
Whole thread Raw
In response to Re: global barrier & atomics in signal handlers (Re: Atomic operations within spinlocks)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: global barrier & atomics in signal handlers (Re: Atomic operations within spinlocks)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Thu, Jun 18, 2020 at 11:59 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Sure, but wouldn't making the SpinLockAcquire layer into static inlines be
> sufficient to address that point, with no need to touch s_lock.h at all?

I mean, wouldn't you then end up with a bunch of 1-line functions
where you can step into the function but not through whatever
individual things it does?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: jsonpath versus NaN
Next
From: Robert Haas
Date:
Subject: Re: jsonpath versus NaN