[HACKERS] Partitions: \d vs \d+

Hi,

Using hash partitions I noticed that \d gives

D=# \d T_p63               Table "public.T_p63"    Column     |     Type      | Collation | Nullable | Default
---------------+---------------+-----------+----------+---------

<remove>

Partition of: T FOR VALUES WITH (modulus 64, remainder 63)
No partition constraint
Indexes:    "T_p63" btree (X, Y)

where as \d+ gives

D=# \d+ T_p63               Table "public.T_p63"    Column     |     Type      | Collation | Nullable | Default | 
Storage  | Stats target | Description
---------------+---------------+-----------+----------+---------+----------+--------------+-------------

<remove>

Partition of: T FOR VALUES WITH (modulus 64, remainder 63)
Partition constraint: satisfies_hash_partition(64, 63, 
hashint4extended(X, '8816678312871386367'::bigint))
Indexes:    "T_p63" btree (X, Y)

E.g. "No partition constraint" vs. "Partition constraint: 
satisfies_hash_partition(...)".

Current master (7769fc000) with [1] and [2].

[1] https://commitfest.postgresql.org/14/1059/
[2] https://commitfest.postgresql.org/14/1089/

Best regards, Jesper


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers