Re: REASSIGN OWNED vs. relisshared dep on !relisshared - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: REASSIGN OWNED vs. relisshared dep on !relisshared
Date
Msg-id 40935c681b3649e8e12cbde4fe86e24a619bc12c.camel@j-davis.com
Whole thread
In response to Re: REASSIGN OWNED vs. relisshared dep on !relisshared  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: REASSIGN OWNED vs. relisshared dep on !relisshared
List pgsql-hackers
On Wed, 2026-07-15 at 20:53 +0530, Dilip Kumar wrote:
> Thanks for the review

Looks good to me, thank you for the patch. I will commit this soon.

To address Noah's concern: is the concern about the dependency link, or
about having a database-specific oid in a shared catalog at all?

If the former, then we could do the same work manually outside of the
pg_depend mechanism.

If the latter, we could decompose pg_subscription into the columns
necessary for the launcher (shared catalog) and the database-specific
columns (unshared catalog). But that's more invasive so it might not be
v19 material.

Thoughts?

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Semih Doğan
Date:
Subject: [PATCH] pgbench: fix incorrect long option name in error message
Next
From: surya poondla
Date:
Subject: Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL