| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Add psql command to list constraints |
| Date: | 2021-11-16 04:23:04 |
| Message-ID: | CAKFQuwYSr=kdNstKCc5_PR0GTiZ=GYcDwnR_AynPvg6R7yUxsg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday, November 15, 2021, Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp>
wrote:
>
>
> I don't know if this is a good example, but if you look at StackOverflow,
> it seems that people who want to see a list of constraints appear
> regularly.
https://stackoverflow.com/questions/62987794/how-to-list-all
> -constraints-of-a-table-in-postgresql
>
>
Given the questioner restricted their question to “for a given table” I’d
say it supports leaving the status quo, not changing it.
If, as you suppose, these come up regularly then finding one that asks for
it “in the entire database”, ideally with some stated goal, should be
doable.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2021-11-16 04:44:26 | Re: Added schema level support for publication. |
| Previous Message | Tatsuro Yamada | 2021-11-16 04:11:20 | Re: Add psql command to list constraints |