| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Samed YILDIRIM <samed(at)reddoc(dot)net> |
| Cc: | Teju Jakkidi vlogs <teja(dot)jakkidi05(at)gmail(dot)com>, Holger Jakobs <holger(at)jakobs(dot)com>, pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Duplicate data even with primary keys enabled |
| Date: | 2022-10-29 15:26:24 |
| Message-ID: | 14712.1667057184@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Samed YILDIRIM <samed(at)reddoc(dot)net> writes:
> Hi Teja,
> Your columns are varchar. They may seem the same to you due to the tool you
> use. But, it doesn't mean they are identical. There can be leading or
> trailing spaces.
Another thing I'm wondering about is index corruption due to an
operating-system upgrade that changed string sort ordering.
Nothing might be obviously wrong right after the upgrade, but
index searches would probably fail to find existing entries,
which could lead to not rejecting duplicate entries.
This is, sadly, not at all hypothetical or uncommon.
There's some info about this hazard at:
https://wiki.postgresql.org/wiki/Locale_data_changes
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amine Tengilimoglu | 2022-10-30 10:42:42 | pgbouncer client disconnect while server was not ready log |
| Previous Message | Scott Ribe | 2022-10-29 15:20:22 | Re: Duplicate data even with primary keys enabled |