From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: no default hash partition |
Date: | 2019-08-07 16:29:45 |
Message-ID: | 20190807162945.GA28711@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-Aug-07, Amit Langote wrote:
> That hash-partitioned tables can't have default partition is mentioned
> in the CREATE TABLE page:
>
> "If DEFAULT is specified, the table will be created as a default
> partition of the parent table. The parent can either be a list or
> range partitioned table. A partition key value not fitting into any
> other partition of the given parent will be routed to the default
> partition. There can be only one default partition for a given parent
> table."
Actually, it also says this (in the blurb for the PARTITION OF clause):
Creates the table as a <firstterm>partition</firstterm> of the specified
parent table. The table can be created either as a partition for specific
values using <literal>FOR VALUES</literal> or as a default partition
using <literal>DEFAULT</literal>. This option is not available for
hash-partitioned tables.
which I think is sufficient.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2019-08-07 16:33:08 | Re: Grouping isolationtester tests in the schedule |
Previous Message | Tom Lane | 2019-08-07 16:28:22 | Rethinking opclass member checks and dependency strength |