Re: Removing "long int"-related limit on hash table sizes
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Munro <thomas.munro@gmail.com>, Jeff Davis <pgsql@j-davis.com>, pgsql-hackers@lists.postgresql.org
Date: 2021-07-27T16:52:33Z
Lists: pgsql-hackers
Hi, On 2021-07-26 11:38:41 +0900, Michael Paquier wrote: > On Sun, Jul 25, 2021 at 12:28:04PM -0400, Tom Lane wrote: > > Andres Freund <andres@anarazel.de> writes: > >> We really ought to just remove every single use of long. > > > > I have no objection to that as a long-term goal. But I'm not volunteering > > to do all the work, and in any case it wouldn't be a back-patchable fix. > > I feel that we do need to do something about this performance regression > > in v13. > > Another idea may be to be more aggressive in c.h? A tweak there would > be dirtier than marking long as deprecated, but that would be less > invasive. Any of that is not backpatchable, of course.. Hard to see how that could work - plenty system headers use long... Greetings, Andres Freund
Commits
-
Get rid of artificial restriction on hash table sizes on Windows.
- b154ee63bb65 14.0 landed
- 2b8f3f5a7c0e 13.4 landed
- 28d936031a86 15.0 landed