Re: Add primary keys to system catalogs
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>
Cc: Craig Ringer <craig.ringer@enterprisedb.com>,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>,
Joel Jacobson <joel@compiler.org>
Date: 2021-01-21T07:41:04Z
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/
Commits
-
Add primary keys and unique constraints to system catalogs
- dfb75e478cac 14.0 landed