| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Jayson Hreczuck <jayson(dot)hreczuck(at)studentuniverse(dot)com> |
| Cc: | abbas alizadeh <ramkly(at)yahoo(dot)com>, Erik Wienhold <ewie(at)ewie(dot)name>, 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:20:22 |
| Message-ID: | 0E92AFA3-CD35-4B25-90AE-D1E46420E90B@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Oct 29, 2022, at 8:40 AM, Jayson Hreczuck <jayson(dot)hreczuck(at)studentuniverse(dot)com> wrote:
>
> Very curious about this too. Corruption of indexes does occur but less than a handful of times in my 30 years of DBA experience, and is usually due to hardware failure or some immediate cause.
I've seen it once because of bad hardware, and once because of collation changes with a Linux upgrade. That latter one was tricky, because it wasn't limited to just non-7-bit characters, but also how hyphens (or maybe it was underscores) were handled.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-10-29 15:26:24 | Re: Duplicate data even with primary keys enabled |
| Previous Message | Samed YILDIRIM | 2022-10-29 15:06:14 | Re: Duplicate data even with primary keys enabled |