Re: pg_restore --create --no-tablespaces should not issue 'CREATEDATABASE ... TABLESPACE' - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: pg_restore --create --no-tablespaces should not issue 'CREATEDATABASE ... TABLESPACE'
Date
Msg-id CAB7nPqQLxi+h7AmWRQaDg+jQyW-E+Z4-ZiKq+8jVSES+vKcRvw@mail.gmail.com
Whole thread Raw
In response to pg_restore --create --no-tablespaces should not issue 'CREATEDATABASE ... TABLESPACE'  (eike <eike@rikart.de>)
Responses Re: pg_restore --create --no-tablespaces should not issue 'CREATEDATABASE ... TABLESPACE'  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
On Sat, Dec 16, 2017 at 6:26 AM, eike <eike@rikart.de> wrote:
> I'd say this is a bug in pg_restore.
>
> When invoking pg_restore with the option --no-tablespaces
> the statement: CREATE DATABASE
> should create the database in the current table space,
> ignoring any table space designation from the export.

Per the documentation in
https://www.postgresql.org/docs/devel/static/app-pgrestore.html:
Do not output commands to select tablespaces. With this option, all
objects will be created in whichever tablespace is the default during
restore.

So it seems to me that this is a justified complain. Thoughts?
-- 
Michael


pgsql-bugs by date:

Previous
From: Devrim Gündüz
Date:
Subject: Re: BUG #14980: initddb fails (Issue with postgresql-9.3 initdconfig)
Next
From: Ashutosh Sharma
Date:
Subject: Re: 10.1: hash index size exploding on vacuum full analyze