From: John Scalia <jayknowsunix@gmail.com>
To: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump weirdness
Date: Mon, 8 Nov 2021 09:38:19 -0500
Message-ID: <d8c36c37-14aa-79a7-2c62-e051e797b59f@gmail.com> (raw)
In-Reply-To: <b3e479d6-0f1e-25fd-72bb-f0cdadff067b@sqlexec.com>
References: <492eb0ca-d43e-e732-61bd-17293fff431a@gmail.com>
<b3e479d6-0f1e-25fd-72bb-f0cdadff067b@sqlexec.com>
I determined what the problem was this morning, there was one error
about a foreign key violation, which I did not really see earlier. so I
removed two foreign key constraints from the target table. The load then
worked properly, and some 600k records are now loaded.
On 11/6/2021 9:25 AM, MichaelDBA wrote:
> I think you are pointing to the wrong binaries.
>
> Use the absolute path to your pg_dump binary to make sure you are
> using the version you think you are using. For example:
> /usr/pgsql-11/bin/pg_dump -h original_server -t
> original_schema.table_name -U user -W dbname > table_name.sql
>
> And for the target do the same for psql plus add the stop on error parm:
> /usr/pgsql-11/bin/psql -h target_server -U user newdbname -v
> ON_ERROR_STOP=1 < table_name.sql
>
> Regards,
> Michael Vitale
>
>
>
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: pgsql-admin@postgresql.org
Cc: jayknowsunix@gmail.com, MichaelDBA@sqlexec.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_dump weirdness
In-Reply-To: <d8c36c37-14aa-79a7-2c62-e051e797b59f@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 DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox