MIME-Version: 1.0
In-Reply-To: <CAHAc2jeB+Mzm1Kz-4Uq2CN=EGxdJO17tE0Aqm20BQUV9rGr1QQ@mail.gmail.com>
References: <CAHAc2jeB+Mzm1Kz-4Uq2CN=EGxdJO17tE0Aqm20BQUV9rGr1QQ@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Sat, 22 Jun 2024 23:02:55 -0700
Message-ID: <CAKFQuwZu8Q94nrhKFWADvap3n0OhNS5D_+Apk7NEBjxfjU6NGw@mail.gmail.com>
Subject: Re: pg_dump restores as expected on some machines and reports
 duplicate keys on others
To: Shaheed Haque <shaheedhaque@gmail.com>
Cc: pgsql-general list <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000073d229061b886a2b"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwZu8Q94nrhKFWADvap3n0OhNS5D_%2BApk7NEBjxfjU6NGw%40mail.gmail.com>
Precedence: bulk

--00000000000073d229061b886a2b
Content-Type: text/plain; charset="UTF-8"

On Saturday, June 22, 2024, Shaheed Haque <shaheedhaque@gmail.com> 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.

--00000000000073d229061b886a2b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Saturday, June 22, 2024, Shaheed Haque &lt;<a href=3D"mailto:shaheedhaqu=
e@gmail.com">shaheedhaque@gmail.com</a>&gt; wrote:<blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div dir=3D"ltr"><div><ul><li>The one difference I can think of betwe=
en deployment pairs which work ok, and those which fail is that the logic V=
M (i.e. where the psql client script runs) is the use of a standard AWS ubu=
ntu image for the OK case, versus a custom AWS image for the failing case.<=
/li><ul><li>The custom image is a saved snapshot of one created using the s=
tandard image.<br></li></ul></ul><div>Why should the use of one type of VM =
image versus another cause pg_restore to hallucinate the duplicate records?=
</div></div></div></blockquote><div><br></div><div>To tie the other comment=
s to your description: you took/have a snapshot of the base image after you=
 created the database and added some records to it.=C2=A0 Nothing wrong her=
e - you just need to decide how you want to deal with the situation.</div><=
div><br></div><div>David J.</div><div><br></div>

--00000000000073d229061b886a2b--