Re: Add psql command to list constraints

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Add psql command to list constraints
Date: 2021-11-16 02:02:15
Message-ID: 20211116020214.GV17618@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks for updating the patch :)

> Currently, DBAs need the table name to see the constraint information.

Or, they can query pg_constraint or information_schema: check_constraints,
table_constraints.

> - success = listConversions(pattern, show_verbose, show_system);
> + if (strncmp(cmd, "dco", 3) == 0) /* Constraint */
> + switch (cmd[3])
> + {
> + case '\0':
> + case '+':

Does "+" do anything ?

> +++ b/src/bin/psql/help.c
> @@ -231,6 +231,7 @@ slashUsage(unsigned short int pager)

> fprintf(output, _(" \\db[+] [PATTERN] list tablespaces\n"));
> fprintf(output, _(" \\dc[S+] [PATTERN] list conversions\n"));
> + fprintf(output, _(" \\dco[S] [PATTERN] list constraint\n"));

Should be plural "constraints".

I think "exclude" should be called "exclusion" ("exclude" sounded to me like
you're going to provide a way to "exclude" types of constraints, like "xc"
would show everything except check constraints).

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2021-11-16 02:08:56 Re: Add psql command to list constraints
Previous Message Alexander Korotkov 2021-11-16 02:00:08 Re: Slow standby snapshot