MIME-Version: 1.0
In-Reply-To: <CAKFQuwZu8Q94nrhKFWADvap3n0OhNS5D_+Apk7NEBjxfjU6NGw@mail.gmail.com>
References: <CAHAc2jeB+Mzm1Kz-4Uq2CN=EGxdJO17tE0Aqm20BQUV9rGr1QQ@mail.gmail.com>
 <CAKFQuwZu8Q94nrhKFWADvap3n0OhNS5D_+Apk7NEBjxfjU6NGw@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Sat, 22 Jun 2024 23:07:37 -0700
Message-ID: <CAKFQuwY5M7KXr9KA0R4UWBoQr7gPsRUkUz9V5KbCCCvPMJCuCw@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="000000000000498ffd061b887beb"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwY5M7KXr9KA0R4UWBoQr7gPsRUkUz9V5KbCCCvPMJCuCw%40mail.gmail.com>
Precedence: bulk

--000000000000498ffd061b887beb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Saturday, June 22, 2024, David G. Johnston <david.g.johnston@gmail.com>
wrote:

> 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 ps=
ql
>>    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 o=
f
> 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 wi=
th
> 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=E2=80=99t going to be com=
plaining
about things (especially the database) existing.

David J.

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

On Saturday, June 22, 2024, David G. Johnston &lt;<a href=3D"mailto:david.g=
.johnston@gmail.com">david.g.johnston@gmail.com</a>&gt; wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">On Saturday, June 22, 2024, Shaheed Haque &lt;<a href=
=3D"mailto:shaheedhaque@gmail.com" target=3D"_blank">shaheedhaque@gmail.com=
</a>&gt; wrote:<blockquote class=3D"gmail_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 between deployment pairs which work ok, =
and those which fail is that the logic VM (i.e. where the psql client scrip=
t runs) is the use of a standard AWS ubuntu image for the OK case, versus a=
 custom AWS image for the failing case.</li><ul><li>The custom image is a s=
aved snapshot of one created using the standard image.<br></li></ul></ul><d=
iv>Why should the use of one type of VM image versus another cause pg_resto=
re to hallucinate the duplicate records?</div></div></div></blockquote><div=
><br></div><div>To tie the other comments to your description: you took/hav=
e a snapshot of the base image after you created the database and added som=
e records to it.=C2=A0 Nothing wrong here - you just need to decide how you=
 want to deal with the situation.</div></blockquote><div><br></div><div>Sor=
ry, but to be clear/clarify - you must be using an RDS snapshot as well as =
an EC2 snapshot, a fresh built RDS cluster isn=E2=80=99t going to be compla=
ining about things (especially the database) existing.</div><div><br></div>=
<div>David J.</div>

--000000000000498ffd061b887beb--