From: Tom Lane <tgl@sss.pgh.pa.us>
To: akdmnnakdm@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17534: 'tablespace' option crushes 'create database' query
 with 'permission denied' message
In-reply-to: <17534-fcb8fb4c81cd17b6@postgresql.org>
References: <17534-fcb8fb4c81cd17b6@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 28 Jun 2022 08:39:21 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2699998.1656439696.1@sss.pgh.pa.us>
Date: Tue, 28 Jun 2022 14:08:16 -0400
Message-ID: <2699999.1656439696@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2699999.1656439696%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> If some user with createdb privilege would try to create database with
> 'tablespace = pg_default' option, query will fail with ERROR:  42501
> But same query without  'tablespace = pg_default' option would work fine,
> and new database will be created at pg_default tablespace as expected.

I do not think this is a bug.  The default tablespace is determined
by (copied from) the template database you use, and a user without
any tablespace-related privileges shouldn't be able to override that.

			regards, tom lane