public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: pg_restore failed on foreign key constraint
Date: Fri, 13 Feb 2026 15:17:36 -0500
Message-ID: <CANzqJaCybV8TjOODr8XFEzjNLLGeUzEuWNhVXGGepDxAZLR70A@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CANzqJaD1JNeJfNJkxZOvqSw=ueJLzq3hM3tUf5FJNkbxEr8Z4A@mail.gmail.com>
<[email protected]>
<CANzqJaB3rHWWHQD2aUqrQvZcdo_doOKTNFcMkBnkvoTt4_JriA@mail.gmail.com>
<[email protected]>
<CANzqJaDbrmgAXmctgFR62o22+CMYnNjmKd06uX9RD3jjUj9u=Q@mail.gmail.com>
<[email protected]>
<CANzqJaB-Sb_KXJZGB++9n9ymMLC0_YB876acX1tNNdjsPskbWw@mail.gmail.com>
<[email protected]>
On Fri, Feb 13, 2026 at 12:35 PM Adrian Klaver <[email protected]>
wrote:
[snip]
> >
> > 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?
>
Yes it does. 😀
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: pg_restore failed on foreign key constraint
In-Reply-To: <CANzqJaCybV8TjOODr8XFEzjNLLGeUzEuWNhVXGGepDxAZLR70A@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox