Re: pg_restore creates public schema?

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_restore creates public schema?
Date: 2022-10-06 19:35:21
Message-ID: 5bd9bfaa-8221-d2f5-f699-84f23169ad42@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/6/22 09:46, Ron wrote:
> On 10/6/22 10:20, Tom Lane wrote:
>> Ron<ronljohnsonjr(at)gmail(dot)com> writes:
>>> 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.
>> But why are you using the dead version's pg_dump? You could use
>> the supported version of that.
>
> Because installing new software on production servers requires hurdles
> (Service Now change ticket approved by the application support manager,
> Delivery Service Manager, Engineering Change Board, and a one week lead
> time before installing during the Saturday night maintenance window)
> that I'm not willing to jump through just to take an /ad hoc/ database
> backup.

1) So I assume that means Postgres 13.8 has not been installed in
anticipation of the change over?

2) All those hoops, yet you can move the data off site with no issue?

>
>
> --
> Angular momentum makes the world go 'round.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2022-10-06 20:52:17 Re: pg_restore creates public schema?
Previous Message Adrian Klaver 2022-10-06 19:32:27 Re: pg_restore creates public schema?