BUG #17732: pg_restore fails with check constraint - Mailing list pgsql-bugs

From David G. Johnston
Subject BUG #17732: pg_restore fails with check constraint
Date
Msg-id CAKFQuwbhscV_3y+PU2dkBa-=rm7wyGLiKnKz8ZvG7xrLb4pUAQ@mail.gmail.com
Whole thread Raw
In response to BUG #17732: pg_restore fails with check constraint  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Tuesday, December 27, 2022, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      17732
Logged by:          Artem
Email address:      artem.voropaev@hotmail.com
PostgreSQL version: 13.9
Operating system:   Debian
Description:       

Hi team! We faced an error using pg_restore on our database. We have
database tables like this one:

Is there any solution for this specific problem?


Unbreak the source system by converting the check constraint into a trigger.  Check constraints, as documented, must be immutable.  Unfortunately the system doesn’t warn you when you’ve violated this rule upfront.

David J.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17733: ERROR: could not load library "/Users/frank/postgres/postgresql-13.9/lib/postgresql/llvmjit.so": dl
Next
From: Justin Pryzby
Date:
Subject: Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue)