| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Removing "long int"-related limit on hash table sizes |
| Date: | 2021-07-27 16:52:33 |
| Message-ID: | 20210727165233.ngfin7otbs2pz4on@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 蔡梦娟 (玊于) | 2021-07-27 16:55:18 | 回复：Why don't update minimum recovery point in xact_redo_abort |
| Previous Message | Fujii Masao | 2021-07-27 16:49:35 | Re: Why don't update minimum recovery point in xact_redo_abort |