Re: 12.1 Partitioned Table Creation Bug

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Chris Drawater <Chris(dot)Drawater(at)viavisolutions(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: 12.1 Partitioned Table Creation Bug
Date: 2020-01-22 21:39:32
Message-ID: CAKFQuwZLsGaz2fS8F-sNxmZMRL=z=AA_BepmP3YxEyVxXEmqig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jan 22, 2020 at 12:48 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Chris Drawater <Chris(dot)Drawater(at)viavisolutions(dot)com> writes:
> > geo=> create table junk ( a int, b int) PARTITION BY RANGE (a);
> > ERROR: cannot specify default tablespace for partitioned relations
>
> I'm guessing you've got default_tablespace set to something nonempty.
>
> I don't know why the decision was made to throw an error rather than
> silently ignoring the setting ...
>

Ignoring the setting seems to be what the documentation says we do:

https://www.postgresql.org/docs/12/sql-createtable.html

"For partitioned tables, since no storage is required for the table itself,
the tablespace specified overrides default_tablespace as the default
tablespace to use for any newly created partitions when no other tablespace
is explicitly specified."

So this seems like a regression in v12.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2020-01-22 23:17:44 Re: 12.1 Partitioned Table Creation Bug
Previous Message Tom Lane 2020-01-22 19:47:57 Re: 12.1 Partitioned Table Creation Bug