| From: | jonathan(dot)katz(at)excoventures(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #8813: Clarifying OVERLAPS in the Docs |
| Date: | 2014-01-13 04:25:21 |
| Message-ID: | 20140113042521.30126.87682@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 8813
Logged by: Jonathan S. Katz
Email address: jonathan(dot)katz(at)excoventures(dot)com
PostgreSQL version: 9.3.2
Operating system: N/A
Description:
This was reported by Adam Mackler (mackler) in the doc comments, and am
relaying this. My edits are in []
========
Section 9.9 (v. 9.3 manual) says "the SQL OVERLAPS operator is supported."
There is no entry in the [documentation] index for "OVERLAPS." I've been
operating for some time now on the mistaken assumption that OVERLAPS was not
supported, simply because I assumed that if it were, then there would be an
index entry for it.
I propose modifying the [documentation] index by adding an "OVERLAPS" entry.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | thehappycoder | 2014-01-13 06:57:28 | BUG #8816: to_tsquery returns wrong results |
| Previous Message | sfrost | 2014-01-13 04:12:35 | BUG #8812: Testing, testing |