Re: BUG #18609: Repeated installcheck failure in test_pg_dump due to existing role

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: n(dot)kalinin(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18609: Repeated installcheck failure in test_pg_dump due to existing role
Date: 2024-09-19 07:44:58
Message-ID: ZuvWeodtN9qwt6Dw@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Junwang Zhao 2024-09-19 09:27:04 Re: BUG #18624: Memory Leak Issue with PostgreSQL Connection During COPY Command Execution.
Previous Message PG Bug reporting form 2024-09-19 07:30:54 BUG #18624: Memory Leak Issue with PostgreSQL Connection During COPY Command Execution.