Re: managing primary key conflicts while restoring data to table with existing data

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Rob Sargent <robjsargent(at)gmail(dot)com>
Cc: Krishnakant Mane <kkmane(at)riseup(dot)net>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: managing primary key conflicts while restoring data to table with existing data
Date: 2019-09-25 17:44:36
Message-ID: CAHOFxGqze037=anQVyWpN=08BtciuNnvN9eWUTyHp2CXfATdnw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> If the data is held in common tables(bills, vouchers, etc)then the only
> thing I see happening is changing the PK values to an unused value. That
> could turn into a nightmare though. Not only that you lose the connection
> to the original data source. If the data can be broken out into separate
> tables then I could see placing them in their own schema.
>
>
Why not have separate databases for each "restore"? They can run together
on one machine still. What is the user doing with this copy of the data?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Paul Jungwirth 2019-09-25 18:09:53 Re: Pg_auto_failover
Previous Message Tom Lane 2019-09-25 16:00:39 Re: Upgrading old server