On Wed, Aug 9, 2017 at 8:18 AM, Rajkumar Raghuwanshi <rajkumar.raghuwan...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
