| 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-15 13:10:52 |
| Message-ID: | CAPpHfdvx1vbyvuip93oo7C2F3O22+FiUVZw_mKjjvbAqJsTkCQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jun 13, 2021 at 2:48 PM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> 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?
I heard no objection. So, pushed.
------
Regards,
Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-06-15 13:13:21 | Re: doc issue missing type name "multirange" in chapter title |
| Previous Message | Alexander Korotkov | 2021-06-15 13:10:21 | Re: unnesting multirange data types |