Re: Experimenting with hash tables inside pg_dump
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2021-10-22T20:32:39Z
Lists: pgsql-hackers
I wrote: > Andres Freund <andres@anarazel.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
Commits
-
In pg_dump, use simplehash.h to look up dumpable objects by OID.
- 92316a4582a5 15.0 landed
-
Fix frontend version of sh_error() in simplehash.h.
- 974aedcea46d 15.0 landed
- 8cee4be6dc93 14.1 landed
- 2e01d050d989 13.5 landed