Re: pg_dump fail to not dump public schema orders

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: "David G. Johnston" <david.g.johnston@gmail.com>

Cc: Adrien Nayrat <adrien.nayrat@anayrat.info>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2020-05-29T14:40:20Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Improve pg_dump's handling of "special" built-in objects.
- 5955d934194c 11.0 cited

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Friday, May 29, 2020, Adrien Nayrat <adrien.nayrat@anayrat.info> wrote:
>> I noticed pg_dump failed to not dump creation or comment commands for
>> public schema when we explicitly ask it to dump public schema.

> As far as I can tell this is working as intended/documented.  The public
> schema doesn’t and doesn’t and shouldn’t get special treatment relative to
> any other user schema here.

Note this is something we intentionally changed a little while ago
(v11, looks like), along with a larger refactoring of pg_dump vs.
pg_dumpall.  But yeah, public is not treated differently from other
schemas anymore.

			regards, tom lane