On 7/24/23 09:09, Tom Lane wrote:
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>> The error message is misleading, you can’t directly create tables in a
>> database, you must create them in a schema and the permission to do so is
>> granted to the role on the schema, not the database.
> The actual server message is going to be just
>
> ERROR: permission denied for schema public
>
> I'm not sure where the "Are you sure ..." bit came from, but it wasn't
> Postgres.
>
> Anyway, backing up two steps, it looks like drupal hasn't yet adapted
> to the v15 change that removed default create privileges on the public
> schema (for security reasons). You might see if a newer drupal release
> is available. If not, the best bet would likely be
>
> GRANT ALL ON SCHEMA public TO public;
I'd have naively expected "GRANT ALL ON SCHEMA public TO public; " to be
taken care of by "GRANT ALL PRIVILEGES ON DATABASE cbdevdb TO cbdevdbadmin;".
--
Born in Arizona, moved to Babylonia.
