Re: pg_dump weirdness - Mailing list pgsql-admin

From John Scalia
Subject Re: pg_dump weirdness
Date
Msg-id d8c36c37-14aa-79a7-2c62-e051e797b59f@gmail.com
Whole thread Raw
In response to Re: pg_dump weirdness  (MichaelDBA <MichaelDBA@sqlexec.com>)
List pgsql-admin

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



pgsql-admin by date:

Previous
From: Tyler Brock
Date:
Subject: Re: Segfault during queries
Next
From: Tom Lane
Date:
Subject: Re: Postgres dying after many failed logins