Re: [PATCH v1] Fix for bug #19773 : pg_dump differing generation expressions of inherited columns

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: assam258(at)gmail(dot)com
Cc: Nitin Motiani <nitinmotiani(at)google(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH v1] Fix for bug #19773 : pg_dump differing generation expressions of inherited columns
Date: 2026-11-03 06:52:47
Message-ID: CAExHW5vHZwb3wzQjKnobGYs35wYu56nhJRAdhn6sCkA4kyUOEQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 3, 2026 at 11:28 AM Henson Choi <assam258(at)gmail(dot)com> wrote:
>
> Hi Nitin,
>
> I have looked at v2. Below are my notes on the multi-parent scenario,
> and on how the backend problem where the restored child loses its
> inherited CHECK constraint shows up with v2.

I didn't look at the whole patch and don't intend to review. I noticed
that this patch adds tests to pg_dump TAP test. Instead, we should
check whether we can leverage 002_pg_upgrade for this testing - if
there are test in regression suite that render the objects in the
required state, leave them in regression database at the end. If the
tests do not do that, probably we are missing respective DDL coverage
in regression suite itself.

--
Best Wishes,
Ashutosh Bapat

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-11-03 07:13:16 Re: Avoid duplicate file references in backend .pot file
Previous Message vignesh C 2026-11-03 06:47:18 Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication