Re: Default Partition for Range
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>
Cc: Beena Emerson <memissemerson@gmail.com>,
Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>, Rahila Syed <rahilasyed90@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>,
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-08-09T12:23:48Z
Lists: pgsql-hackers
On Wed, Aug 9, 2017 at 8:18 AM, Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com> wrote: > --difference in the description of default partition in case of list vs > range > > create table lp (a int) partition by list(a); > create table lp_d partition of lp DEFAULT; > postgres=# \d+ lp_d > Table "public.lp_d" > Column | Type | Collation | Nullable | Default | Storage | Stats target > | Description > --------+---------+-----------+----------+---------+---------+--------------+------------- > a | integer | | | | plain | > | > Partition of: lp DEFAULT > Partition constraint: > > create table rp (a int) partition by range(a); > create table rp_d partition of rp DEFAULT; > postgres=# \d+ rp_d > Table "public.rp_d" > Column | Type | Collation | Nullable | Default | Storage | Stats target > | Description > --------+---------+-----------+----------+---------+---------+--------------+------------- > a | integer | | | | plain | > | > Partition of: rp DEFAULT > Partition constraint: true This looks like a problem with the default list partitioning patch. I think "true" is what we expect to see here in both cases. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Allow a partitioned table to have a default partition.
- 6f6b99d1335b 11.0 landed
-
Add new files to nls.mk and add translation markers
- 5ff3d73813eb 10.0 cited
-
Improve release note text about set-returning-function changes.
- a12c09ad86e6 10.0 cited