| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
| Cc: | "shihao zhong" <zhong950419(at)gmail(dot)com>, Jian He <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: EXCLUDE COLLATE in CREATE/ALTER TABLE document |
| Date: | 2024-04-07 19:38:44 |
| Message-ID: | 2908108.1712518724@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Daniel Verite" <daniel(at)manitou-mail(dot)org> writes:
> Also the use of "and/or" in the previous version conveys the fact
> that operator class and ordering options are not mutually
> exclusive. But when using "any of the following" in the new text,
> doesn't it loose that meaning?
Yeah; and/or is perfectly fine here and doesn't need to be improved
on.
There's a bigger problem though, which is that these bits
are *also* missing any reference to opclass parameters.
I fixed that and pushed it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Wienhold | 2024-04-07 19:46:58 | Re: ❓ JSON Path Dot Precedence |
| Previous Message | Pavel Borisov | 2024-04-07 19:15:00 | Re: Table AM Interface Enhancements |