Search Postgresql Archives

Re: pg_dump restores as expected on some machines and reports duplicate keys on others

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Saturday, June 22, 2024, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote:
On Saturday, June 22, 2024, Shaheed Haque <shaheedhaque@xxxxxxxxx> wrote:
  • The one difference I can think of between deployment pairs which work ok, and those which fail is that the logic VM (i.e. where the psql client script runs) is the use of a standard AWS ubuntu image for the OK case, versus a custom AWS image for the failing case.
    • The custom image is a saved snapshot of one created using the standard image.
Why should the use of one type of VM image versus another cause pg_restore to hallucinate the duplicate records?

To tie the other comments to your description: you took/have a snapshot of the base image after you created the database and added some records to it.  Nothing wrong here - you just need to decide how you want to deal with the situation.

Sorry, but to be clear/clarify - you must be using an RDS snapshot as well as an EC2 snapshot, a fresh built RDS cluster isn’t going to be complaining about things (especially the database) existing.

David J.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux