Re: Missing pg_depend entries for constraints created by extensions (deptype 'e')

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joel Jacobson" <joel(at)compiler(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Missing pg_depend entries for constraints created by extensions (deptype 'e')
Date: 2025-05-31 21:56:12
Message-ID: 3008018.1748728572@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joel Jacobson" <joel(at)compiler(dot)org> writes:
> Foreign key constraints created during CREATE EXTENSION
> lack a pg_depend entry with deptype='e'.

Why would it be a sensible thing for an extension to create a
foreign-key constraint on table(s) that it didn't itself create?
(If it did create them, the indirect dependency seems sufficient.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-05-31 23:55:15 Re: tighten generic_option_name, or store more carefully in catalog?
Previous Message Joel Jacobson 2025-05-31 21:10:53 Missing pg_depend entries for constraints created by extensions (deptype 'e')