| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, "Peter Eisentraut" <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Subject: | Re: Recording foreign key relationships for the system catalogs |
| Date: | 2021-02-02 20:05:01 |
| Message-ID: | 70cd42c9-333c-457a-967d-5da58594b23b@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 2, 2021, at 17:00, Tom Lane wrote:
>No, I think it's correct as-is (and this is one reason that I chose to
>have two separate FK entries for cases like this). confrelid can be
>zero in rows that are not FK constraints. However, such a row must
>also have empty confkey. The above entry states that for each element
>of confkey, the pair (confrelid,confkey[i]) must be nonzero and have
>a match in pg_attribute. It creates no constraint if confkey is empty.
Thanks for explaining, I get it now.
>Appreciate the review! Please confirm if you agree with above
>analysis.
Yes, I agree with the analysis.
/Joel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michail Nikolaev | 2021-02-02 20:31:00 | Re: Thoughts on "killed tuples" index hint bits support on standby |
| Previous Message | Pavel Stehule | 2021-02-02 19:54:47 | Re: bugfix - plpgsql - statement counter is incremented 2x for FOR stmt |