| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dump fail to not dump public schema orders |
| Date: | 2020-05-29 14:40:20 |
| Message-ID: | 10317.1590763220@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Friday, May 29, 2020, Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrien Nayrat | 2020-05-29 14:42:21 | Re: pg_dump fail to not dump public schema orders |
| Previous Message | Tom Lane | 2020-05-29 14:28:47 | Re: proposal: possibility to read dumped table's name from file |