Re: Switching to NOINHERIT user triggers #XX000 error

From: Dominique Devienne <ddevienne(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Switching to NOINHERIT user triggers #XX000 error
Date: 2024-11-05 18:29:04
Message-ID: CAFCRh-_du9nVxpFVc9WV62TsMK=7+NTWnCG3K8QLmOrQ4Xs0WQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Nov 5, 2024 at 7:25 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dominique Devienne <ddevienne(at)gmail(dot)com> writes:
> > On Tue, Nov 5, 2024 at 6:42 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matt Zagrabelny 2024-11-05 21:45:15 adsrc
Previous Message Tom Lane 2024-11-05 18:25:21 Re: Switching to NOINHERIT user triggers #XX000 error