| From: | Alexander Kukushkin <cyberdemn(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dump: assert failure sorting casts/transforms |
| Date: | 2026-10-02 07:25:42 |
| Message-ID: | CAFh8B=kyXjy=1NzACXsD7LFS3rfAsWmpdXbWDs5f4=1C8uG8pw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Noah,
sorry that it took so long to get back.
On Wed, 9 Sept 2026 at 02:04, Noah Misch <noah(at)leadboat(dot)com> wrote:
> Since this is already the fourth follow-up to my original change, I had
> Opus 5
> look for more ways to reach the assertion. It found one more:
>
> D1 DO_POLICY: the "RLS enabled" pseudo-object borrows its table's
> relname, so
> it ties with a policy named after that same table. An assert-enabled
> pg_dump aborts; a production build orders the two by comparing a
> pg_class
> OID against a pg_policy OID, which pg_upgrade inverts.
>
> Let's fix that at the same time. Would you like to add that, or would you
> like me to add it?
>
Please find the attached v4 version of the patch that also handles RLS
policies.
--
Regards,
--
Alexander Kukushkin
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-pg_dump-sort-casts-and-transforms-rls-v4.patch | text/x-patch | 8.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-10-02 07:30:21 | Re: Adding a stored generated column without long-lived locks |
| Previous Message | Alexandre Felipe | 2026-10-02 07:22:10 | Re: Throwing away unnecessary spin-locks |