Re: elog(DEBUG2 in SpinLocked section. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: elog(DEBUG2 in SpinLocked section.
Date
Msg-id CA+TgmoandgaD=+SznpsNEuyFPRTpAT0mGCrkMrbPr_rvL_fsFQ@mail.gmail.com
Whole thread Raw
In response to Re: elog(DEBUG2 in SpinLocked section.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: elog(DEBUG2 in SpinLocked section.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jun 3, 2020 at 12:36 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Should we think about adding automated detection of this type of
> mistake?  I don't like the attached as-is because of the #include
> footprint expansion, but maybe we can find a better way.

I think it would be an excellent idea.

Removing some of these spinlocks and replacing them with LWLocks might
also be worth considering.

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Bump default wal_level to logical
Next
From: Tom Lane
Date:
Subject: Re: elog(DEBUG2 in SpinLocked section.