Re: Errors when restoring backup created by pg_dumpall
Adrian Klaver <adrian.klaver@aklaver.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>,
pgsql-general <pgsql-general@postgresql.org>
Date: 2024-12-06T03:48:37Z
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.g.johnston@gmail.com <mailto:david.g.johnston@gmail.com>> wrote: > > On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson <ronljohnsonjr@gmail.com > <mailto:ronljohnsonjr@gmail.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.klaver@aklaver.com
Commits
-
contrib/earthdistance: Use SQL-standard function bodies.
- 969bbd0fafc0 18.0 landed
- 3652de36e432 17.3 landed
- 31daa10facec 16.7 landed