Problem with COPY command on pg_dump

Started by Blake McBrideover 8 years ago4 messagesgeneral
Jump to latest
#1Blake McBride
blake@mcbride.name

Greetings,

I am using pg_dump on version 9.5.10 and trying to import it on version
9.3.20. Many (or all) COPY commands are failing with messages like:

psql:16504.db:16874: ERROR: missing data for column "street"
CONTEXT: COPY address, line 1: ""

Is there an easy way for me to fix this (like export with some
compatibility flag)?

Thanks!

Blake McBride

#2Rob Sargent
robjsargent@gmail.com
In reply to: Blake McBride (#1)
Re: Problem with COPY command on pg_dump

On Dec 9, 2017, at 8:42 AM, Blake McBride <blake@mcbride.name> wrote:

Greetings,

I am using pg_dump on version 9.5.10 and trying to import it on version 9.3.20. Many (or all) COPY commands are failing with messages like:

psql:16504.db:16874: ERROR: missing data for column "street"
CONTEXT: COPY address, line 1: ""

Is there an easy way for me to fix this (like export with some compatibility flag)?

Thanks!

Blake McBride

Is there in fact ‘street’ data in the file? Sounds like you have the wrong number of columns. Do you have your actual dump and restore commands to show here?

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Rob Sargent (#2)
Re: Problem with COPY command on pg_dump

Rob Sargent <robjsargent@gmail.com> writes:

On Dec 9, 2017, at 8:42 AM, Blake McBride <blake@mcbride.name> wrote:
I am using pg_dump on version 9.5.10 and trying to import it on version 9.3.20. Many (or all) COPY commands are failing with messages like:
psql:16504.db:16874: ERROR: missing data for column "street"
CONTEXT: COPY address, line 1: ""

Is there in fact ‘street’ data in the file? Sounds like you have the wrong number of columns. Do you have your actual dump and restore commands to show here?

While pg_dump certainly does sometimes produce output that doesn't reload
into older servers, we try to minimize such problems --- and in any case,
the actual COPY data shouldn't be a source of issues. I'm suspicious that
the true problem occurred earlier; maybe a table drop/creation failed
and now COPY is trying to load into a pre-existing table that has the
right name and the wrong column list.

I'd counsel looking at the *first* error message and resolving that,
then trying again. Anything later could just be cascaded failures.

regards, tom lane

#4Blake McBride
blake@mcbride.name
In reply to: Rob Sargent (#2)
Re: Problem with COPY command on pg_dump

I suppose it's something I'm doing. I'm pg_dump'ing the schema with the
data, so I can't be missing any columns. However, I wrote a program to
filter out certain data. I believe that is where the problem is. I wrote
it a long, long time ago before --exclude-table-data existed. When I
use --exclude-table-data
it works.

Thanks.

Blake

On Sat, Dec 9, 2017 at 9:53 AM, Rob Sargent <robjsargent@gmail.com> wrote:

Show quoted text

On Dec 9, 2017, at 8:42 AM, Blake McBride <blake@mcbride.name> wrote:

Greetings,

I am using pg_dump on version 9.5.10 and trying to import it on version

9.3.20. Many (or all) COPY commands are failing with messages like:

psql:16504.db:16874: ERROR: missing data for column "street"
CONTEXT: COPY address, line 1: ""

Is there an easy way for me to fix this (like export with some

compatibility flag)?

Thanks!

Blake McBride

Is there in fact ‘street’ data in the file? Sounds like you have the
wrong number of columns. Do you have your actual dump and restore commands
to show here?