Re: pg_dump crash due to incomplete ordering of DO_SUBSCRIPTION_REL objects - Mailing list pgsql-hackers

From Noah Misch
Subject Re: pg_dump crash due to incomplete ordering of DO_SUBSCRIPTION_REL objects
Date
Msg-id 20251218211002.53.nmisch@google.com
Whole thread Raw
In response to Re: pg_dump crash due to incomplete ordering of DO_SUBSCRIPTION_REL objects  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
On Thu, Dec 18, 2025 at 05:35:45PM +0530, vignesh C wrote:
> On Thu, 18 Dec 2025 at 14:05, Chao Li <li.evan.chao@gmail.com> wrote:
> > > On Dec 18, 2025, at 03:51, Noah Misch <noah@leadboat.com> wrote:
> > > I plan to push the attached version.
> > > <DO_SUBSCRIPTION_REL-v4.patch>

Pushed as d49936f etc.

> > 2
> > ```
> > +               /* Sort by subscription name, since (namespace, name) match the rel */
> > ```
> >
> > This comment is correct, but sounds a little insider-ish. Maybe:
> >
> > /* Tiebreak by subscription name; (namespace, name) already identify the table */
> 
> Similarly here too, it is inline with similar comments of other enums
> in this function.

Exactly.  For cosmetics, consistency with nearby code is the stronger rule.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_plan_advice
Next
From: Dharin Shah
Date:
Subject: Re: Fwd: [PATCH] Add zstd compression for TOAST using extended header format