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

public inbox for [email protected]  
help / color / mirror / Atom feed

From: David G. Johnston <[email protected]>
To: Shaheed Haque <[email protected]>
Cc: pgsql-general list <[email protected]>
Subject: Re: pg_dump restores as expected on some machines and reports duplicate keys on others
Date: Sat, 22 Jun 2024 23:02:55 -0700
Message-ID: <CAKFQuwZu8Q94nrhKFWADvap3n0OhNS5D_+Apk7NEBjxfjU6NGw@mail.gmail.com> (raw)
In-Reply-To: <CAHAc2jeB+Mzm1Kz-4Uq2CN=EGxdJO17tE0Aqm20BQUV9rGr1QQ@mail.gmail.com>
References: <CAHAc2jeB+Mzm1Kz-4Uq2CN=EGxdJO17tE0Aqm20BQUV9rGr1QQ@mail.gmail.com>

On Saturday, June 22, 2024, Shaheed Haque <[email protected]> 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.

David J.

view thread (4+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: pg_dump restores as expected on some machines and reports duplicate keys on others
  In-Reply-To: <CAKFQuwZu8Q94nrhKFWADvap3n0OhNS5D_+Apk7NEBjxfjU6NGw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox