public inbox for [email protected]  
help / color / mirror / Atom feed
From: David G. Johnston <[email protected]>
To: PopeRigby <[email protected]>
Cc: Adrian Klaver <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Errors when restoring backup created by pg_dumpall
Date: Mon, 9 Dec 2024 15:31:52 -0700
Message-ID: <CAKFQuwYYrLxVCaQbKgXszOmUWNXAGxiKPCa8GQS7DFWxSiZoiQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<CAKFQuwaB5GuUNuyiUbS0ah-LYXepHLPnOHrP7g8RMz8ywOm3zQ@mail.gmail.com>
	<[email protected]>
	<CAKFQuwYQUequkYVS8SLgC1L0TOdWNK=xVyxnPD9RPPwfvYRFSQ@mail.gmail.com>
	<[email protected]>
	<CAKFQuwbe4TSU_LxsrGxgcv4DfQq2x-UNoyKx-ABy36PhvbGCdg@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAKFQuwZf+1frb+82G2-2tD84GXEpuCG_WZaiAU46=L2PDa9gYw@mail.gmail.com>
	<[email protected]>

On Mon, Dec 9, 2024 at 3:14 PM PopeRigby <[email protected]> wrote:

> On 12/7/24 11:58, David G. Johnston wrote:
>
> On Sat, Dec 7, 2024 at 12:25 PM PopeRigby <[email protected]> wrote:
>
>>
>> It actually looks like setting those all to have public fixed all the
>> errors, including the one with lldap. So, how can I get it to not put
>> public there automatically for next time?
>>
>>
> I assume you mean "get it to put public there" (i.e., the "not" is a typo)
>
> You cannot.  The security team has decided to not permit an opt-in bypass
> of the lock-downs implemented to fix CVE-2018-1058.
>
> Your only real choice at the moment is to replace the function call in the
> generated expression with a custom function and in that custom function's
> create function command attach a "set search_path to public" clause.  That
> will prevent inlining and also ensure the public schema is in the
> search_path when executing the public.ll_to_earth function call.  With that
> in place the empty search_path in the dump file will no longer matter.
>
> Yeah, that was a typo. It seems weird that this behavior would be broken
> by default though, is there anything that could fix it upstream?
>

You saw and tried the work being done "upstream" to fix the situation.
It's a big knot in the system and it isn't easy (or highly motivated) to
untangle unfortunately...

David J.


view thread (20+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Errors when restoring backup created by pg_dumpall
  In-Reply-To: <CAKFQuwYYrLxVCaQbKgXszOmUWNXAGxiKPCa8GQS7DFWxSiZoiQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox