From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | PopeRigby <poperigby(at)mailbox(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Errors when restoring backup created by pg_dumpall |
Date: | 2024-12-01 21:14:18 |
Message-ID: | 1470486.1733087658@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 12/1/24 12:05, PopeRigby wrote:
>> I'm still getting this error:
>>
>> psql:all.sql:4102: ERROR: type "earth" does not exist
>> LINE 1: ...ians($1))*sin(radians($2))),earth()*sin(radians($1)))::earth
> The issue is still this:
> SELECT pg_catalog.set_config('search_path', '', false);
> in the pg_dumpall output.
We've done that for some time, though.
> As was suggested before change the above to:
> SELECT pg_catalog.set_config('search_path', 'public', false);
> in the pg_dumpall output file.
I'm betting that won't help. The new-in-17 behavior is that
maintenance commands such as CREATE INDEX internally force
a "safe" search_path, regardless of the prevailing setting.
It would be useful to know what is the command at line 4102
of all.sql.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Kleiner | 2024-12-01 21:21:34 | Re: Connection to 127.0.0.1 refused in a Dockerfile based on postgres:17-alpine3.20 |
Previous Message | Adrian Klaver | 2024-12-01 21:12:50 | Re: Connection to 127.0.0.1 refused in a Dockerfile based on postgres:17-alpine3.20 |