Re: Row count mismatch post pg_dump piped restore - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Row count mismatch post pg_dump piped restore
Date
Msg-id CAKFQuwZWiis4j2t5d+=yRz7XYv5c9Tyody+ET5rtNu=mFVdL7g@mail.gmail.com
Whole thread Raw
In response to Row count mismatch post pg_dump piped restore  (chandrakant sharma <mike.ck007@gmail.com>)
List pgsql-bugs
On Mon, Feb 15, 2016 at 4:27 AM, chandrakant sharma <mike.ck007@gmail.com>
wrote:

> Hello Team,
>
> I tried using the following command line argument to restore a table on
> the fly using pg_dump. The source and target dbs are GP. The process
> completed successfully however, the number of rows in the target were
> higher than as compared to source. The difference was greater the 1K  row=
s.
>
> Here is the command line used:
> pg_dump -a -x -U remote_user -h remote_server -t table_to_copy source_db =
|
> psql target_db
>
> Version of pg_dump being used:
> pg_dump (PostgreSQL) 8.4.20
>
>
=E2=80=8BI suspect that target table already existed in target_db and conta=
ined
data.=E2=80=8B  All you did was append the records from remote_server to th=
e 1k
that were already present.

David J.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #13958: Missing docs on error
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #13961: Unexpected behaviour of JSONB_SET if the new_value is null