| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | chu_z(at)hotmail(dot)com |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Correction |
| Date: | 2022-07-24 19:39:17 |
| Message-ID: | 1737957.1658691557@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
PG Doc comments form <noreply(at)postgresql(dot)org> writes:
> "If you declare a column as UNIQUE or PRIMARY KEY, the implicitly generated
> index is case-sensitive. So it's useless for case-insensitive searches, and
> it won't enforce uniqueness case-insensitively."
> I think the statement above is not correct. I tried creating a PK or unique
> key index on a CITEXT column. It checks uniqueness in case-insensitivity.
That paragraph is talking about what happens when you *don't* use citext.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-07-24 19:41:11 | Re: Bug in code sample in "8.15.5. Searching in Arrays" |
| Previous Message | yanliang lei | 2022-07-24 04:01:40 | pg document is not recorded：maintenance_work_mem can not large than 2GB in windows |