From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: default partitions can be partitioned and have default partitions? |
Date: | 2019-09-30 01:54:10 |
Message-ID: | CA+HiwqG6j=Vh_r-HCeO_EQQCnoESWqk7mCaXh1U0wCg5OFVFQw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Sep 29, 2019 at 12:18 AM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> postgres=# CREATE TABLE t(i int)PARTITION BY RANGE(i);
> CREATE TABLE
> postgres=# CREATE TABLE t0 PARTITION OF t DEFAULT PARTITION BY RANGE(i);
> CREATE TABLE
> postgres=# CREATE TABLE t00 PARTITION OF t0 DEFAULT; -- oh yes
> CREATE TABLE
Actually, you can go even further
CREATE TABLE t00 PARTITION OF t0 DEFAULT PARTITION BY HASH (i);
> Not sure how it could be useful to partition default into subpartitions of
> lists, ranges, hashes.
Yeah, maybe the top-level partitioning should be designed such that
the default partition doesn't need sub-partitioning, but perhaps
Postgres shouldn't prevent users from trying it. This was discussed
when the default partition feature went in; see [1].
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-09-30 03:42:41 | Re: recovery_min_apply_delay in archive recovery causes assertion failure in latch |
Previous Message | Fujii Masao | 2019-09-30 01:48:53 | Re: Standby accepts recovery_target_timeline setting? |