| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "artem(dot)voropaev(at)hotmail(dot)com" <artem(dot)voropaev(at)hotmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | BUG #17732: pg_restore fails with check constraint |
| Date: | 2022-12-28 17:08:26 |
| Message-ID: | CAKFQuwbhscV_3y+PU2dkBa-=rm7wyGLiKnKz8ZvG7xrLb4pUAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tuesday, December 27, 2022, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 17732
> Logged by: Artem
> Email address: artem(dot)voropaev(at)hotmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-12-28 20:13:23 | Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue) |
| Previous Message | PG Bug reporting form | 2022-12-28 16:15:27 | BUG #17733: ERROR: could not load library "/Users/frank/postgres/postgresql-13.9/lib/postgresql/llvmjit.so": dl |