| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info> |
| Cc: | 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 13:56:36 |
| Message-ID: | CAKFQuwZGgrcLXNQhXt-Mo2uXayQZuKfFc=aDv-Kd+fwCuoPkcw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday, May 29, 2020, Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info> wrote:
> Hello,
>
> I noticed pg_dump failed to not dump creation or comment commands for
> public
> schema when we explicitly ask it to dump public schema.
>
> Shorter example: pg_dump -n public dump will give:
> [Create schema public....]
>
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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2020-05-29 13:58:49 | Re: Make the qual cost on index Filter slightly higher than qual cost on index Cond. |
| Previous Message | Ashutosh Bapat | 2020-05-29 13:52:01 | Re: Speeding up parts of the planner using a binary search tree structure for nodes |