Re: LogwrtResult contended spinlock - Mailing list pgsql-hackers

From Tom Lane
Subject Re: LogwrtResult contended spinlock
Date
Msg-id 2741228.1719845958@sss.pgh.pa.us
Whole thread Raw
In response to Re: LogwrtResult contended spinlock  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: LogwrtResult contended spinlock
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Maybe we can do something like this,

> +#if MAXIMUM_ALIGNOF >= 8
>      uint64        currval;

This should probably be testing the alignment of int64 specifically,
rather than assuming that MAXIMUM_ALIGNOF applies to it.  At least
historically, there have been platforms where MAXIMUM_ALIGNOF is
determined by float quantities and integer quantities are different.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: LogwrtResult contended spinlock
Next
From: "David E. Wheeler"
Date:
Subject: jsonpath: Inconsistency of timestamp_tz() Output