Re: Errors when restoring backup created by pg_dumpall

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Errors when restoring backup created by pg_dumpall
Date: 2024-12-06 03:48:37
Message-ID: 09e17634-f0a7-4fd6-9901-f76daf8654a7@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/5/24 18:44, Ron Johnson wrote:
> On Thu, Dec 5, 2024 at 6:24 PM David G. Johnston
> <david(dot)g(dot)johnston(at)gmail(dot)com <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>> wrote:
>
> On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com
> <mailto:ronljohnsonjr(at)gmail(dot)com>> wrote:
>
> Another alternative is to open the .sql file in Notepad++, then
> add "public." before all the unqualified "earth" and
> "ll_to_earth" references.
>
>
> And as discussed there are none in that file because those
> references are within an extension's objects and only create
> extension appears in the file.
>
>
> Then why would changing search_path work?

Because that is set for each database before the objects in that
database are created. That means anything that is created subsequently
will be have access to all other objects created in the path. This would
include objects created indirectly from an extension as well as objects
that include non-schema qualified names.

>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2024-12-06 05:06:42 Re: Errors when restoring backup created by pg_dumpall
Previous Message Ron Johnson 2024-12-06 02:44:07 Re: Errors when restoring backup created by pg_dumpall