Re: pg_dump crash due to incomplete ordering of DO_SUBSCRIPTION_REL objects

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dump crash due to incomplete ordering of DO_SUBSCRIPTION_REL objects
Date: 2025-12-18 08:35:14
Message-ID: 361EFB90-5AF0-4647-9FAC-3CD34661B467@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Dec 18, 2025, at 03:51, Noah Misch <noah(at)leadboat(dot)com> wrote:
>
> On Wed, Dec 17, 2025 at 10:11:58AM +0530, vignesh C wrote:
>> The attached v3 version patch has the changes for the same.
>
> The "tag" variable needed a change to compensate for the subrinfo->dobj.name
> change. I plan to push the attached version.
> <DO_SUBSCRIPTION_REL-v4.patch>

v4 looks solid. A couple of nitpicks:

1
```
+ SubRelInfo *srobj1 = *(SubRelInfo *const *) p1;
+ SubRelInfo *srobj2 = *(SubRelInfo *const *) p2;
```

These two temp pointers can be const, like:
```
const SubRelInfo *srobj1 = *(SubRelInfo *const *) p1;
const SubRelInfo *srobj2 = *(SubRelInfo *const *) p2;
```

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 */

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2025-12-18 08:44:33 Re: Parallel Apply
Previous Message Amit Langote 2025-12-18 08:20:00 Re: Segmentation fault on proc exit after dshash_find_or_insert