Re: BUG #18405: flaw in dump of inherited/dropped constraints

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18405: flaw in dump of inherited/dropped constraints
Date: 2024-03-29 02:03:31
Message-ID: 0C77E12D-E40C-4501-817A-1564FB984E9E@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On Mar 25, 2024, at 10:11 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Given the way pg_dump works, that's pretty hard to believe: you
> should get bitwise the same result from pg_dump to text versus
> pg_dump -Fc | pg_restore. Can you provide a self-contained test
> showing a case where it doesn't?

Retried exactly what I though I had done previously. Nope, you are right. I must have screwed up a step.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-03-29 04:44:27 BUG #18417: Excessive log messages on warm standby server
Previous Message PG Bug reporting form 2024-03-28 23:27:36 BUG #18416: Confirmation of Issue with PostgreSQL ODBC Driver for Windows