pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix crashes with CREATE SCHEMA AUTHORIZATION and schema elements
Date: Fri, 28 Apr 2023 10:30:37 +0000
Message-ID: <E1psLN6-005Jam-8q@gemulon.postgresql.org> (raw)

Fix crashes with CREATE SCHEMA AUTHORIZATION and schema elements

CREATE SCHEMA AUTHORIZATION with appended schema elements can lead to
crashes when comparing the schema name of the query with the schemas
used in the qualification of some clauses in the elements' queries.

The origin of the problem is that the transformation routine for the
elements listed in a CREATE SCHEMA query uses as new, expected, schema
name the one listed in CreateSchemaStmt itself.  However, depending on
the query, CreateSchemaStmt.schemaname may be NULL, being computed
instead from the role specification of the query given by the
AUTHORIZATION clause, that could be either:
- A user name string, with the new schema name being set to the same
value as the role given.
- Guessed from CURRENT_ROLE, SESSION_ROLE or CURRENT_ROLE, with a new
schema name computed from the security context where CREATE SCHEMA is
running.

Regression tests are added for CREATE SCHEMA with some appended elements
(some of them with schema qualifications), covering also some role
specification patterns.

While on it, this simplifies the context structure used during the
transformation of the elements listed in a CREATE SCHEMA query by
removing the fields for the role specification and the role type.  They
were not used, and for the role specification this could be confusing as
the schema name may by extracted from that at the beginning of
CreateSchemaCommand().

This issue exists for a long time, so backpatch down to all the versions
supported.

Reported-by: Song Hongyu
Author: Michael Paquier
Reviewed-by: Richard Guo
Discussion: https://postgr.es/m/17909-f65c12dfc5f0451d@postgresql.org
Backpatch-through: 11

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/d29eba1987cb1ae2520e1534e53cc13b720e7e38

Modified Files
--------------
src/backend/commands/schemacmds.c           |  3 +-
src/backend/parser/parse_utilcmd.c          | 38 +++++------
src/include/parser/parse_utilcmd.h          |  3 +-
src/test/regress/expected/create_schema.out | 98 +++++++++++++++++++++++++++++
src/test/regress/parallel_schedule          |  2 +-
src/test/regress/sql/create_schema.sql      | 70 +++++++++++++++++++++
6 files changed, 192 insertions(+), 22 deletions(-)



view thread (6+ messages)

Message-ID: <E1psLN6-005Jam-8q@gemulon.postgresql.org>
Permalink:  ../E1psLN6-005Jam-8q@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1psLN6-005Jam-8q@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: michael@paquier.xyz, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Fix crashes with CREATE SCHEMA AUTHORIZATION and schema elements
  In-Reply-To: <E1psLN6-005Jam-8q@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox