Re: BUG #18609: Repeated installcheck failure in test_pg_dump due to existing role
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: n.kalinin@postgrespro.ru, pgsql-bugs@lists.postgresql.org
Date: 2024-09-19T07:44:58Z
Lists: pgsql-bugs
On Wed, Sep 11, 2024 at 10:01:22AM +0200, Daniel Gustafsson wrote: > That would be backpatching 936e3fa3787a51397280c1081587586e83c20399. I haven't > checked if there are complications in doing so but I think it should be quite > straightforward. As far as I can see it would be enough to add the DROP OWNED BY to avoid the random notice messages listing the dependencies the role depends on, followed by the DROP ROLE. FWIW, I am not seeing any complications (the TAP test recreates the same role name regress_dump_test_role on its own), so let's just do it. -- Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Drop global objects after completed test
- 936e3fa3787a 17.0 cited