| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: doc issue missing type name "multirange" in chapter title |
| Date: | 2021-06-13 11:48:10 |
| Message-ID: | CAPpHfdtwnNXnS5goAFnryHmwF8FGuGgXtiDZ7NFLo5qoMUR7vg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 11, 2021 at 11:16 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> > What about "Range/Multirange Functions and Operators"?
>
> Better than a comma, I guess. Personally I didn't have a
> problem with the form with two "ands".
Thank you. I propose to push the slash option because it both evades
double "and" and it's aligned with sibling section headers (we have
"Date/Time Functions and Operators").
Any objections?
------
Regards,
Alexander Korotkov
| Attachment | Content-Type | Size |
|---|---|---|
| docs-title-range-multirange.patch | application/x-patch | 449 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2021-06-13 12:01:48 | Re: An out-of-date comment in nodeIndexonlyscan.c |
| Previous Message | Alexander Korotkov | 2021-06-13 11:43:36 | Re: unnesting multirange data types |