Re: pg_dump: assert failure sorting casts/transforms

From: Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com>
To: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dump: assert failure sorting casts/transforms
Date: 2026-08-22 13:59:01
Message-ID: CAMm1aWaGo34ifu6W=Ad3vefrcMDDDvUHG2UxXYU399GBMEP4Jw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> here is v3 version of the patch addressing all nit-picks

Thanks for the v3 patch. It addresses my earlier comments, and the fix
and regression coverage look good to me. I have no other comments.

One optional follow-up thought: the current tests exercise the
assertion-failure case well. Order-aware checks could additionally
verify the OID-independent ordering property and help detect future
regressions to an OID fallback. I realize the earlier natural-key
ordering changes do not consistently include explicit output-order
checks either, so I do not think this should delay the current patch
or require a v4. If there is interest, I can investigate a separate
follow-up patch for suitable coverage of this case and the earlier
OID-independence cases.

Since the issue also affects REL_19_STABLE, I think the fix should be
applied there along with master. No older back-branches appear to be
affected.

Best Regards,
Nitin Jadhav
Azure Database for PostgreSQL
Microsoft

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 贾明伟 2026-08-22 13:59:11 Subject: [RFC] Umbra: Reducing Full-Page Write Amplification through Physical Page Remapping
Previous Message Alexander Lakhin 2026-08-22 13:00:01 028_pitr_timelines.pl might fail when cp interrupted and backup includes required segment