From: | Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Partitions: \d vs \d+ |
Date: | 2017-09-28 13:02:37 |
Message-ID: | 2af5fc4d-7bcc-daa8-4fe6-86274bea363c@redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Maksim Milyutin | 2017-09-28 13:19:48 | Re: Partitions: \d vs \d+ |
Previous Message | Yugo Nagata | 2017-09-28 12:55:24 | Re: Optional message to user when terminating/cancelling backend |