From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | Maksim Milyutin <milyutinma(at)gmail(dot)com>, Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Partitions: \d vs \d+ |
Date: | 2017-09-29 20:03:41 |
Message-ID: | CA+TgmoY06OTxiHQK7_8GtehonCyyN8QRVe3CWxpnpEe_b46ycA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 28, 2017 at 9:33 PM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Perhaps, there is no case when "No partition constraint" should be output,
> but I may be missing something.
The case arises when a partitioned table has a default partition but
no other partitions.
I have committed the patch.
In v10, it's impossible to have a partition with no partition
constraint, and if it does happen due to some bug, the worst that will
happen is \d will just print nothing, rather than explicitly printing
that there's no constraint. That's not a serious problem and it
shouldn't happen anyway, so no back-patch.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2017-09-29 20:17:22 | Re: Arrays of domains |
Previous Message | Robert Haas | 2017-09-29 19:53:02 | Re: UPDATE of partition key |