| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Joel Jacobson <joel(at)compiler(dot)org> |
| Subject: | Re: Add primary keys to system catalogs |
| Date: | 2021-01-21 07:41:04 |
| Message-ID: | 37c18f90-fd2a-993f-0527-1a06049ab8bb@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-01-18 18:23, Tom Lane wrote:
> The reason I got interested in this right now is the nearby
> discussion [1] about why findoidjoins misses some catalog
> relationships and whether we should fix that and/or make its results
> more readily accessible. I'd thought perhaps FK constraint entries
> could supersede the need for that tool altogether, but now it seems
> like not.
Yes, catalog consistency checking was also something I had in mind.
There are clearly a number of complications still to resolve. But in
general the idea of representing relationships between tables in the
DDL/schema sounds like a sensible idea.
--
Peter Eisentraut
2ndQuadrant, an EDB company
https://www.2ndquadrant.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-01-21 08:01:15 | Re: OpenSSL connection setup debug callback issue |
| Previous Message | Peter Eisentraut | 2021-01-21 07:39:03 | Re: Add primary keys to system catalogs |