public inbox for [email protected]help / color / mirror / Atom feed
Re: Switching to NOINHERIT user triggers #XX000 error 3+ messages / 2 participants [nested] [flat]
* Re: Switching to NOINHERIT user triggers #XX000 error @ 2024-11-05 18:21 Dominique Devienne <[email protected]> 2024-11-05 18:25 ` Re: Switching to NOINHERIT user triggers #XX000 error Tom Lane <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Dominique Devienne @ 2024-11-05 18:21 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: [email protected] On Tue, Nov 5, 2024 at 6:42 PM Tom Lane <[email protected]> wrote: > Dominique Devienne <[email protected]> writes: > > On v16 and v17 though, it works with INHERIT, but with NOINHERIT, I get: > > GRANT "...:USER" TO "ddevienne" #XX000: ERROR: no possible grantors > > Any clue to what this means, so I can start looking in the right place? > > \errverbose in psql would help you locate what part of the code > is throwing that. (Or if triggering it from psql is not convenient, > set log_error_verbosity = verbose and find the info in the postmaster > log.) > > 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. Hi Tom. 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. I trapped the error in the code, and here's the details ERROR: XX000: no possible grantors LOCATION: check_role_grantor, user.c:2229 I used PQresultVerboseErrorMessage(). Tell me if you need some other error field This is against a 17.0 server, for the line number above. If I shared (privately) a libpq client-side trace with you Tom, would that help you? This particular test, I could redesign to work-around this issue probably. But this is not the only tests that fails with a NOINHERIT user on v16+, and I haven't tracked down all the reasons yet... PS: I can't easily get server-side logs ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Switching to NOINHERIT user triggers #XX000 error 2024-11-05 18:21 Re: Switching to NOINHERIT user triggers #XX000 error Dominique Devienne <[email protected]> @ 2024-11-05 18:25 ` Tom Lane <[email protected]> 2024-11-05 18:29 ` Re: Switching to NOINHERIT user triggers #XX000 error Dominique Devienne <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Tom Lane @ 2024-11-05 18:25 UTC (permalink / raw) To: Dominique Devienne <[email protected]>; +Cc: [email protected] Dominique Devienne <[email protected]> writes: > On Tue, Nov 5, 2024 at 6:42 PM Tom Lane <[email protected]> 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? regards, tom lane ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Switching to NOINHERIT user triggers #XX000 error 2024-11-05 18:21 Re: Switching to NOINHERIT user triggers #XX000 error Dominique Devienne <[email protected]> 2024-11-05 18:25 ` Re: Switching to NOINHERIT user triggers #XX000 error Tom Lane <[email protected]> @ 2024-11-05 18:29 ` Dominique Devienne <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Dominique Devienne @ 2024-11-05 18:29 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: [email protected] On Tue, Nov 5, 2024 at 7:25 PM Tom Lane <[email protected]> wrote: > Dominique Devienne <[email protected]> writes: > > On Tue, Nov 5, 2024 at 6:42 PM Tom Lane <[email protected]> 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2024-11-05 18:29 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-11-05 18:21 Re: Switching to NOINHERIT user triggers #XX000 error Dominique Devienne <[email protected]> 2024-11-05 18:25 ` Tom Lane <[email protected]> 2024-11-05 18:29 ` Dominique Devienne <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox