Horton

Re: v13: Performance regression related to FORTIFY_SOURCE

Jeff Davis <pgsql@j-davis.com>

View thread View on postgr.es
From: Jeff Davis <pgsql@j-davis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, pgsql-hackers@postgresql.org, Peter Geoghegan <pg@bowt.ie>
Date: 2020-06-06T02:06:50Z
Lists: 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

Commits

  1. Fix platform-specific performance regression in logtape.c.