Re: managing primary key conflicts while restoring data to table withexisting data - Mailing list pgsql-general

From Michael Lewis
Subject Re: managing primary key conflicts while restoring data to table withexisting data
Date
Msg-id CAHOFxGqze037=anQVyWpN=08BtciuNnvN9eWUTyHp2CXfATdnw@mail.gmail.com
Whole thread Raw
In response to Re: managing primary key conflicts while restoring data to table with existing data  (Rob Sargent <robjsargent@gmail.com>)
List 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?

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Upgrading old server
Next
From: Paul Jungwirth
Date:
Subject: Re: Pg_auto_failover