Re: pg_restore failed on foreign key constraint

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_restore failed on foreign key constraint
Date: 2026-02-13 16:05:03
Message-ID: CANzqJaDbrmgAXmctgFR62o22+CMYnNjmKd06uX9RD3jjUj9u=Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Feb 13, 2026 at 10:55 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:

> On 2/13/26 06:18, Ron Johnson wrote:
> > On Fri, Feb 13, 2026 at 1:43 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at
> > <mailto:laurenz(dot)albe(at)cybertec(dot)at>> wrote:
>
> > 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.
>
> Is it in the dump file from the source?
>

Some tables aren't being dumped at the source; Thus, the missing records.

--
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 Adrian Klaver 2026-02-13 16:09:21 Re: Index (primary key) corrupt?
Previous Message Adrian Klaver 2026-02-13 15:55:17 Re: pg_restore failed on foreign key constraint