Feedback-ID: ia2694551:Fastmail
Date: Tue, 26 Mar 2024 08:30:45 +0100
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: jian he <jian.universality@gmail.com>, 
	Peter Eisentraut <peter@eisentraut.org>, Aleksander Alekseev <aleksander@timescale.com>, 
	pgsql-hackers <pgsql-hackers@postgresql.org>, vignesh C <vignesh21@gmail.com>
Subject: Re: Catalog domain not-null constraints
Message-ID: <202403260730.cprszamfv5rx@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAEZATCU=ErvPugySbM5TuUZMRG94ww1hJ15z5W_89ZuJkbm_NA@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/202403260730.cprszamfv5rx%40alvherre.pgsql>
Precedence: bulk

On 2024-Mar-25, Dean Rasheed wrote:

> Also (not this patch's fault), psql doesn't seem to offer a way to
> display domain constraint names -- something you need to know to drop
> or alter them. Perhaps \dD+ could be made to do that?

Ooh, I remember we had offered a patch for \d++ to display these
constraint names for tables, but didn't get around to gather consensus
for it.  We did gather consensus on *not* wanting \d+ to display them,
but we need *something*.  I suppose we should do something symmetrical
for tables and domains.  How about \dD++ and \dt++?

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
Bob [Floyd] used to say that he was planning to get a Ph.D. by the "green
stamp method," namely by saving envelopes addressed to him as 'Dr. Floyd'.
After collecting 500 such letters, he mused, a university somewhere in
Arizona would probably grant him a degree.              (Don Knuth)