Re: Merging two database dumps

[Pavan Teja <pavan.postgresdba@xxxxxxxxx>]

Hi Alex,

For storing duplicate rows, dropping primary and unique indexes is the only way.

One alternative is create a column with timestamp which updates on every insert/update so that timestamp will be primary. Hope it helps.

Regards,

Pavan

On Wed, Jun 13, 2018, 4:47 PM Alex O'Ree <spyhunter99@xxxxxxxxx> wrote:

I have a situation with multiple postgres servers running all with the same databases and table structure. I need to periodically export the data from each of there then merge them all into a single server. On  occasion, it's feasible for the same record (primary key) to be stored in two or more servers

I was using pgdump without the --insert option however I just noticed that pgrestore will stop inserting into a table when the conflict occurs, leaving me with an incomplete set.

Question is what are my other options to skip over the conflicting record when merging? 

From the docs, it appears that making dumps with the --insert option may be the only way to go however performance is an issue. In this case would dropping all indexes help?