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-22T19:41:07Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > Which made me look at the code invoking it from simplehash. I think the patch that made simplehash work in frontend code isn't quite right, because pg_log_error() returns... Indeed, that's broken. I guess we want pg_log_fatal then exit(1). > 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? > The only thought I had wrt the patch is that I'd always create the hash > table. That'd require adding an explicit init function and figuring out where to call it, which we could do but I didn't (and don't) think it's worth the trouble. One more branch here isn't going to matter, especially given that we can't even measure the presumed macro improvement. 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