Re: pg_restore --create --no-tablespaces should not issue 'CREATE DATABASE ... TABLESPACE'

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: eike <eike(at)rikart(dot)de>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: pg_restore --create --no-tablespaces should not issue 'CREATE DATABASE ... TABLESPACE'
Date: 2017-12-15 22:56:49
Message-ID: CAB7nPqQLxi+h7AmWRQaDg+jQyW-E+Z4-ZiKq+8jVSES+vKcRvw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Dec 16, 2017 at 6:26 AM, eike <eike(at)rikart(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ashutosh Sharma 2017-12-16 02:33:53 Re: 10.1: hash index size exploding on vacuum full analyze
Previous Message Devrim Gündüz 2017-12-15 22:24:41 Re: BUG #14980: initddb fails (Issue with postgresql-9.3 initd config)