Re: Row count mismatch post pg_dump piped restore

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: chandrakant sharma <mike(dot)ck007(at)gmail(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Row count mismatch post pg_dump piped restore
Date: 2016-02-15 17:54:11
Message-ID: CAKFQuwZWiis4j2t5d+=yRz7XYv5c9Tyody+ET5rtNu=mFVdL7g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Feb 15, 2016 at 4:27 AM, chandrakant sharma <mike(dot)ck007(at)gmail(dot)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 rows.
>
> 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
>
>
​I suspect that target table already existed in target_db and contained
data.​ All you did was append the records from remote_server to the 1k
that were already present.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2016-02-15 18:03:32 Re: BUG #13961: Unexpected behaviour of JSONB_SET if the new_value is null
Previous Message David G. Johnston 2016-02-15 17:45:18 Re: BUG #13958: Missing docs on error