Re: post-bootstrap init : permission denied pg_description

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: François SIMON <francois(dot)simon(at)free(dot)fr>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: post-bootstrap init : permission denied pg_description
Date: 2024-09-12 17:38:11
Message-ID: 4039017.1726162691@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

=?iso-8859-1?Q?Fran=E7ois?= SIMON <francois(dot)simon(at)free(dot)fr> writes:
> So the problem seems to come from xlc, and only at initdb step.
> I can see that initdb runs a backend postgres in single user mode.
> And this is this backend, when compiled with xlc, that shows :
> FATAL: permission denied for table pg_description

Yeah. This seems like it must be an xlc code-generation bug.
It's got nothing to do with filesystem permissions: you're failing
an ACL check at the logical "table" level, which you should not
be because single-user mode implies superuser permissions.

We do have one buildfarm member building with 64-bit xlc on
AIX 7.1:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hornet&dt=2024-09-11%2003%3A51%3A02

I see that that uses a bunch of odd CFLAGS, but they look like they
are mostly to suppress compiler warnings. Another important bit of
the recipe for AIX is -D_LARGE_FILES=1, but I'm not sure that that
would have any impact during initdb (since we're not dealing with
any large files at that point).

You could perhaps try different -O optimization levels. Also
make sure your xlc is up-to-date.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Koen De Groote 2024-09-12 18:47:21 Re: Logical replication without direct link between publisher and subscriber?
Previous Message François SIMON 2024-09-12 17:20:53 Re: post-bootstrap init : permission denied pg_description