| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Errors when restoring backup created by pg_dumpall |
| Date: | 2024-12-10 04:54:25 |
| Message-ID: | CANzqJaA85SC0SVA7KKJKxPXC3qUog9mXVErQWfZz+arvqvtCsg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Dec 9, 2024 at 11:24 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Monday, December 9, 2024, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
>
>> On Sat, Nov 30, 2024 at 10:36 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
>> wrote:
>> [snip]
>>
>>> In future schema qualify all references.
>>>
>>> For now in the dump file you could search for
>>>
>>> SELECT pg_catalog.set_config('search_path', '', false);
>>>
>>> and set to
>>>
>>> SELECT pg_catalog.set_config('search_path', 'public', false);
>>>
>>
>> What if this had been a pg_dump --format={custom,directory} backup?
>>
>
> pg_restore has a mode where it can dump out SQL to a script instead of
> directly restoring to the database.
>
That Would Be Very, Very Bad if this were a database big enough to have
required a multi-threaded dump.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-12-10 05:31:15 | Re: Errors when restoring backup created by pg_dumpall |
| Previous Message | David G. Johnston | 2024-12-10 04:24:17 | Re: Errors when restoring backup created by pg_dumpall |