| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | De Lan <delandl(at)google(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Cc: | Amit Virmani <avirmani(at)google(dot)com>, Terence Yim <terencey(at)google(dot)com>, Vitalii Tymchyshyn <vitaliit(at)google(dot)com>, Samik Gupta <gupsam(at)google(dot)com>, Albert Shau <ashau(at)google(dot)com> |
| Subject: | Re: Duplicate Primary keys in postgresql tables |
| Date: | 2023-07-22 18:02:52 |
| Message-ID: | d2d462ef-cf27-4dfc-7e26-e8d2aaf2f360@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 7/22/23 10:11, De Lan wrote:
> Hi pgsql community,
>
> Recently we found in a postgresql 11.19.0 alpine table there are two
> rows with duplicate primary keys.
>
>
> *Our questions:*
>
> Any ideas on what might cause this behavior other than the collation? if
> it is a well-known issue in the pgsql community or it really is the
> coalition that's the root cause, do we have mitigation for this kind of
> issue from happening in future?
Don't blindly update containers, test first.
>
>
>
> De,
>
> Thanks!
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gus Spier | 2023-07-22 20:37:39 | Re: Effects of dropping a large table |
| Previous Message | Ken Marshall | 2023-07-22 17:30:38 | Re: Duplicate Primary keys in postgresql tables |