Re: [HACKERS] Patch: Add --no-comments to skip COMMENTs with pg_dump

I wrote:
> I went looking and realized that actually what we're interested in here
> is the plpgsql extension, not the plpgsql language ... and in fact the
> behavior I was thinking of is already there, except for some reason it's
> only applied during binary upgrade. So I think we should give serious
> consideration to the attached, which just removes the binary_upgrade
> condition (and adjusts nearby comments).

In further testing of that, I noticed that it made the behavior of our
other bugaboo, the public schema, rather inconsistent. With this
builtin-extensions hack, the plpgsql extension doesn't get dumped,
whether or not you say "clean". But the public schema does get
dropped and recreated if you say "clean". That's not helpful for
non-superuser users of pg_dump, so I think we should try to fix it.

Hence, the attached updated patch also makes selection of the public
schema use the DUMP_COMPONENT infrastructure rather than hardwired
code.

I note btw that the removed bit in getNamespaces() is flat out wrong
independently of these other considerations, because it makes the SQL
put into an archive file vary depending on whether --clean was specified
at pg_dump time. That's not supposed to happen.

I've also updated the regression test this time, as I think this
is committable.

regards, tom lane