From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: Richard Guo <guofenglinux@gmail.com>, hysong0101@163.com,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id
 INT ) will coredump
In-reply-to: <ZEr/shjg+8TClUm/@paquier.xyz>
References: <17909-f65c12dfc5f0451d@postgresql.org>
 <ZEolfwBHm6+znydH@paquier.xyz>
 <CAMbWs4-f5w+YCzqd90YAS-ogPxoahzfJ7C1QUUo8X+KE=0UC4w@mail.gmail.com>
 <ZEpA1SgNzEqhgCvA@paquier.xyz>
 <CAMbWs49CfOfrMp_AGPiBo7g7BusGf2gy1kGSatm-BYO5aeojvQ@mail.gmail.com>
 <ZEr/shjg+8TClUm/@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
	message dated "Fri, 28 Apr 2023 08:05:22 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1237481.1682639329.1@sss.pgh.pa.us>
Date: Thu, 27 Apr 2023 19:48:49 -0400
Message-ID: <1237482.1682639329@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1237482.1682639329%40sss.pgh.pa.us>
Precedence: bulk

Michael Paquier <michael@paquier.xyz> writes:
> It's actually much trickier than that, on second look, as a RoleSpec
> is embedded in this portion of a query because we need to support
> CURRENT_ROLE, CURRENT_SESSION and SESSION_USER.  For example, this
> query assigns neither role name nor schema name we could rely on at
> transformation for the objects:
> create schema authorization current_role create table aa (a int);

Seems like the answer needs to involve postponing examination of
the contained DDL until we've figured out what the new schema's
name is going to be.

			regards, tom lane