Re: pg_restore failed on foreign key constraint - Mailing list pgsql-general

From Adrian Klaver
Subject Re: pg_restore failed on foreign key constraint
Date
Msg-id a2d3e910-3f6e-42a0-858b-65a90da6ab7c@aklaver.com
Whole thread Raw
In response to Re: pg_restore failed on foreign key constraint  (Ron Johnson <ronljohnsonjr@gmail.com>)
List 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!




pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Index (primary key) corrupt?
Next
From: Anthony DeBarros
Date:
Subject: Best practice for granting folder read/write permission on Windows