| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Shaheed Haque <shaheedhaque(at)gmail(dot)com> |
| Cc: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dump restores as expected on some machines and reports duplicate keys on others |
| Date: | 2024-06-23 06:02:55 |
| Message-ID: | CAKFQuwZu8Q94nrhKFWADvap3n0OhNS5D_+Apk7NEBjxfjU6NGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Saturday, June 22, 2024, Shaheed Haque <shaheedhaque(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-06-23 06:07:37 | Re: pg_dump restores as expected on some machines and reports duplicate keys on others |
| Previous Message | Muhammad Ikram | 2024-06-23 05:53:19 | Re: pg_dump restores as expected on some machines and reports duplicate keys on others |