Re: Errors when restoring backup created by pg_dumpall
| От | Ron Johnson |
|---|---|
| Тема | Re: Errors when restoring backup created by pg_dumpall |
| Дата | |
| Msg-id | CANzqJaA85SC0SVA7KKJKxPXC3qUog9mXVErQWfZz+arvqvtCsg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Errors when restoring backup created by pg_dumpall ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Ответы |
Re: Errors when restoring backup created by pg_dumpall
|
| Список | pgsql-general |
On Mon, Dec 9, 2024 at 11:24 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Monday, December 9, 2024, Ron Johnson <ronljohnsonjr@gmail.com> wrote:On Sat, Nov 30, 2024 at 10:36 PM Adrian Klaver <adrian.klaver@aklaver.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!
В списке pgsql-general по дате отправления: