Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: huseyin(dot)d3r(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
Date: 2026-05-20 13:06:58
Message-ID: CAKAnmmLYXcBSV8i5MVuiwu8tkX-JDGmZtJ38_YbdUTwoDW7xKg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>
> PostgreSQL version: 18.3
> ...

5. Verify orphan records remain in pg_init_privs:erprise Postgres Software
> Products & Tech Support
>

Thanks for providing a failing use case. I ran this on a 18.3 server and
found no orphaned rows - but I used the pg_stat_statements extension
instead of pg_wait_sampling. Could you try your experiment using
pg_stat_statements? And could you also show us the contents of the errant
rows in pg_init_privs for the failing case?

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Etsuro Fujita 2026-05-20 17:46:03 Re: BUG #19484: Segmentation fault triggered by FDW
Previous Message Ayush Tiwari 2026-05-20 12:45:44 Re: BUG #19488: Standby connection fails after dropping on login event trigger enabled always