Re: Evidence of Ownership Issues During Restoration of Extension Member Objects - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
Date
Msg-id CAKFQuwYMWQRdhj0SPiW0KnmwMOi0pEmdyWKeyOxDa+GSb5U6VA@mail.gmail.com
Whole thread Raw
In response to Issue with pg_dump Including Ownership Metadata for pg_trgm Extension in PostgreSQL 17  (AKASH <akashbhujbal7051@gmail.com>)
Responses Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
List pgsql-bugs
On Monday, January 27, 2025, AKASH <akashbhujbal7051@gmail.com> wrote:

Addressing this limitation—either through improved documentation or tooling adjustments—would greatly benefit users managing complex permission models.


That most likely means taking Tom’s email of restrictions and adding them to the documentation somewhere.  We don’t really have a good way to modify tooling to prohibit superusers from doing stuff like this that breaks their system.  But this should not be impacting production use cases if proper testing of backup/restore is happening.

As an aside, none of the use cases are framed to directly motivate why you would take the actions described, so we are still just left seeing unnecessary attempts to make unsupported changes to the system permissions setup and responding with “don’t do that”.  An extension like pg_trgm has little to no security implications necessitating complex permission setup, AFAICS.

David J.

pgsql-bugs by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
Next
From: Tom Lane
Date:
Subject: Re: Evidence of Ownership Issues During Restoration of Extension Member Objects