Re: pg_restore creates public schema?

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_restore creates public schema?
Date: 2022-10-06 15:17:44
Message-ID: 33eb3653-26f1-e6c1-dd16-c43ef93f7624@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/6/22 09:49, Tom Lane wrote:
> Ron <ronljohnsonjr(at)gmail(dot)com> writes:
>> pg_dump 9.6.24
> You realize that that version's been out of support for a year?

Yes, which is why I'm dumping from an EOL cluster, and restoring to a
supported version.

>> Why does pg_restore explicitly create "public" even though public is
>> automatically created when the database is created?
> We fixed that in v11 (see 5955d9341). Evidently the fix requires an
> updated pg_dump more than pg_restore.

Ah.

> However, I believe that only happens with -c, so why are you using both -c and -C?

Because the database might already exist on the target before doing the restore.

--
Angular momentum makes the world go 'round.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2022-10-06 15:20:37 Re: pg_restore creates public schema?
Previous Message Tom Lane 2022-10-06 14:49:31 Re: pg_restore creates public schema?