| From: | Neil Anderson <neil(dot)t(dot)anderson(at)gmail(dot)com> |
|---|---|
| To: | kbrannen(at)pwhome(dot)com |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_catalog tables don't have constraints? |
| Date: | 2017-06-12 03:27:44 |
| Message-ID: | CAEKCySvyEhwqBuDkDVr-gi68q6G3wBFdUTqaUpOgFHdkasQ6dg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> Of course. My plan is to copy the catalogs into a new schema so I can add fk
> constraints and then get something like navicat or datagrip to draw it.
>
Hi. I made some progress on this and I've added all the diagrams and
documentation I've been able to produce so far for v10beta as well as
the tools used here:
https://www.postgrescompare.com/2017/06/11/pg_catalog_constraints.html
I would like to try SchemaSpy but it doesn't seem to like constraints
on oid columns too much so I'll have to work around it somehow. Might
be worth it though since it seems to have a new lease of life at
schemaspy.org
Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2017-06-12 06:10:27 | Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100 |
| Previous Message | David G. Johnston | 2017-06-12 02:24:35 | Re: Inconsistent performance with LIKE and bind variable on long-lived connection |