"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;
If you run into more problems, a more drastic answer might be to
downgrade to whatever drupal considers a supported release of
Postgres.
regards, tom lane
