Re: small pg_dump code cleanup
Neil Conway <neil.conway@gmail.com>
From: Neil Conway <neil.conway@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2024-06-05T17:51:08Z
Lists: pgsql-hackers
On Wed, Jun 5, 2024 at 12:37 PM Nathan Bossart <nathandbossart@gmail.com> wrote: > What about collectXXX() to match similar functions in pg_dump.c (e.g., > collectRoleNames(), collectComments(), collectSecLabels())? > sgtm. > > (2) These functions malloc() a single ntups * sizeof(struct) allocation > and > > then index into it to fill-in each struct before entering it into the > hash > > table. It might be more straightforward to just malloc each individual > > struct. > > That'd increase the number of allocations quite significantly, but I'd be > surprised if that was noticeable outside of extreme scenarios. At the > moment, I'm inclined to leave these as-is for this reason and because I > doubt it'd result in much cleanup, but I'll yield to the majority opinion > here. > As you say, I'd be surprised if the performance difference is noticeable. Personally I don't think the marginal performance win justifies the hit to readability, but I don't feel strongly about it. Neil
Commits
-
pg_dump: Remove some unused return values.
- 8213df9effaf 18.0 landed
-
In pg_dump, use simplehash.h to look up dumpable objects by OID.
- 92316a4582a5 15.0 cited