Re: v13: Performance regression related to FORTIFY_SOURCE

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: v13: Performance regression related to FORTIFY_SOURCE
Date: 2020-06-05 00:58:23
Message-ID: 3842c14ad891c956ae19554d206ecebe1dee45ad.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 2020-04-19 at 16:19 -0700, Peter Geoghegan wrote:
> Is it possible that the issue has something to do with what the
> compiler knows about the alignment of the tapes back when they were a
> flexible array vs. now, where it's a separate allocation? Perhaps I'm
> over reaching, but it occurs to me that MemSetAligned() is itself
> concerned about the alignment of data returned from palloc(). Could
> be
> a similar issue here, too.

Perhaps, but if so, what remedy would that suggest?

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2020-06-05 01:09:15 Re: v13: Performance regression related to FORTIFY_SOURCE
Previous Message David Rowley 2020-06-05 00:26:15 Re: [PATCH] Keeps tracking the uniqueness with UniqueKey