Re: pg_restore failed on foreign key constraint

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_restore failed on foreign key constraint
Date: 2026-02-13 17:35:31
Message-ID: a2d3e910-3f6e-42a0-858b-65a90da6ab7c@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/13/26 8:40 AM, Ron Johnson wrote:
> On Fri, Feb 13, 2026 at 11:14 AM Adrian Klaver

>
> Un-confuse me, how do the below relate?:
>
> "Turns out that there's a nightly cron job that dumps this (and other)
> tables with the "--data-only --disable-triggers" options and then does
> "psql -Xaf mumble.sql" to load them into this database.
>
> But access_email_id=2073 is in the source access_email, so I've got to
> figure out why it's not being loaded into the target."
>
> and
>
> "Some tables aren't being dumped at the source"
>
>
> Table name            Source Dumped   Target Loaded
> public.access_email   No              No
> public.rel_user_email Yes             Yes
>
> Thus, while new and modified records are being added
> to public.access_email at the source, they are not making it to the
> Target database.  That plus "--disable-triggers" lets
> the public.rel_user_email loads succeed on the target even though it
> breaks RI.

This means you know what the issue is now?

>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2026-02-13 20:17:36 Re: pg_restore failed on foreign key constraint
Previous Message Adrian Klaver 2026-02-13 17:32:47 Re: Index (primary key) corrupt?