Re: Switching to NOINHERIT user triggers #XX000 error - Mailing list pgsql-general

From Dominique Devienne
Subject Re: Switching to NOINHERIT user triggers #XX000 error
Date
Msg-id CAFCRh-_du9nVxpFVc9WV62TsMK=7+NTWnCG3K8QLmOrQ4Xs0WQ@mail.gmail.com
Whole thread Raw
In response to Re: Switching to NOINHERIT user triggers #XX000 error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, Nov 5, 2024 at 7:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Dominique Devienne <ddevienne@gmail.com> writes:
> > On Tue, Nov 5, 2024 at 6:42 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> This is probably a bug, at least to the extent that we don't like
> >> XX000 errors to be easily reachable, so please let us know what
> >> you find out.
>
> > Finding where the error is thrown is easy, it's when I'm doing that grant.
> > But the code creates two larguish schemas before that and several ROLEs,
> > so it's not easy to share.
>
> Really, we need a self-contained example case to do anything
> about this.  Maybe you could anonymize the object names in
> your test?

I understand, thanks. I might be able to do that. We'll see. --DD



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Switching to NOINHERIT user triggers #XX000 error
Next
From: Matt Zagrabelny
Date:
Subject: adsrc