| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Experimenting with hash tables inside pg_dump |
| Date: | 2021-10-22 20:32:39 |
| Message-ID: | 2824534.1634934759@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> Wonder if we should mark simplehash's grow as noinline? Even with a single caller it seems better to not inline it to remove register allocator pressure.
> Seems plausible --- you want me to go change that?
Hmm, harder than it sounds. If I remove "inline" from SH_SCOPE then
the compiler complains about unreferenced static functions, while
if I leave it there than adding pg_noinline causes a complaint about
conflicting options. Seems like we need a less quick-and-dirty
approach to dealing with unnecessary simplehash support functions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2021-10-22 20:49:38 | Re: [PATCH] Fix memory corruption in pg_shdepend.c |
| Previous Message | Jeff Davis | 2021-10-22 20:16:54 | Re: add retry mechanism for achieving recovery target before emitting FATA error "recovery ended before configured recovery target was reached" |