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 22:04:47 |
Message-ID: | c542aa19-4238-9708-3cdf-13491982a59e@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/6/22 1:54 PM, Ron wrote:
> On 10/6/22 14:32, Adrian Klaver wrote:
>> On 10/6/22 10:46, Christophe Pettus wrote:
>>>
>>>
>>>> On Oct 6, 2022, at 10:44, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>>>> Sadly, that VM doesn't have nearly enough disk space to hold the
>>>> backup folder.
>>>
>>> Use file mode, and stream the output via scp/ssh to a different machine?
>>>
>>
>> Or Plan B:
>>
>> 1) Use pg_dump 9.6.24 on existing(going EOL) server
>>
>> 2) Set up a 9.6.24 instance somewhere you have control.
>>
>> 3) pg_restore to it.
>>
>> 4) Then use pg_dump 13.8 on the new instance.
>
> While that would certainly work, it's a heck of a lot of extra effort
> for large one-time operations.
>
1) It could be scripted.
2) Nothing to stop you from splitting into schema only dump for the 9.6
--> 9.6 --> 13 restore of schema.
3) Then data only dump restored directly to 13.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Bryn Llewellyn | 2022-10-06 22:24:23 | Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE |
Previous Message | Adrian Klaver | 2022-10-06 22:01:18 | Re: pg_restore creates public schema? |