On 2017/03/06 14:25, Simon Riggs wrote: > On 6 March 2017 at 04:00, Ashutosh Bapat wrote: >> Thinking about how to display partition which are further partitioned, >> there are two options. Assume a partitioned table t1 with partitions >> t1p1, which is further partitioned and t1p2. One could display \d+ t1 >> as >> >> \d+ t1 >> Table "public.t1" >> Column | Type | Collation | Nullable | Default | Storage | Stats >> target | Description >> --------+---------+-----------+----------+---------+---------+--------------+------------- >> a | integer | | not null | | plain | | >> Partition key: RANGE (a) >> Partitions: t1p1 FOR VALUES FROM (0) TO (100), HAS PARTITIONS >> t1p2 FOR VALUES FROM (100) TO (200) >> >> OR >> >> \d+ t1 >> Table "public.t1" >> Column | Type | Collation | Nullable | Default | Storage | Stats >> target | Description >> --------+---------+-----------+----------+---------+---------+--------------+------------- >> a | integer | | not null | | plain | | >> Partition key: RANGE (a) >> Partitions: t1p1 FOR VALUES FROM (0) TO (100), PARTITION BY LIST(a) >> t1p2 FOR VALUES FROM (100) TO (200) >> >> To me the first option looks fine. > > +1 > > lowercase please
+1 Thanks, Amit -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
