Re: v13: Performance regression related to FORTIFY_SOURCE - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: v13: Performance regression related to FORTIFY_SOURCE
Date
Msg-id dd4e9a4c8e7e6d2960f77f8dd509ccced332f907.camel@j-davis.com
Whole thread Raw
In response to Re: v13: Performance regression related to FORTIFY_SOURCE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 2020-06-05 at 21:50 -0400, Tom Lane wrote:
> Or possibly casting the whole thing to int or unsigned int would be
> better.  Point being that I bet it's int vs long that is making the
> difference.

That did it, and it's much more tolerable as a workaround. Thank you.

I haven't tested end-to-end that it solves the problem, but I'm pretty
sure it will.

Regards,
    Jeff Davis





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: v13: Performance regression related to FORTIFY_SOURCE
Next
From: Andres Freund
Date:
Subject: Re: Atomic operations within spinlocks