| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Bryn Llewellyn <bryn(at)yugabyte(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>, Tom Lane PostgreSQL <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Two questions about "pg_constraint" |
| Date: | 2022-08-26 05:49:57 |
| Message-ID: | 19BF09AA-B8B1-4837-905E-F6EAABC3E2E2@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Aug 25, 2022, at 21:43, Bryn Llewellyn <bryn(at)yugabyte(dot)com> wrote:
> [...]
I've read this a few times, and I am having trouble understanding what behavior you were expecting out of PostgreSQL, and what behavior you received that you didn't think was correct. If it is "pg_constraint has a column connamespace, and that appears to be a denormalization since a constraint is always in the same schema as the table it is owned by," I believe Tom explained the reason for that.
If that's not what is concerning you, can you summarize it in a sentence two?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-08-26 06:28:27 | Re: In a partition why 1st time encounter NULL then call minvfunc |
| Previous Message | jian he | 2022-08-26 05:40:49 | In a partition why 1st time encounter NULL then call minvfunc |