From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | droptablestar(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Clarity in partial index example. |
Date: | 2019-04-03 22:31:47 |
Message-ID: | 99a710f1-92e2-e5c7-52ae-a1d61cfacd30@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 4/3/19 6:30 PM, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
>> On 4/3/19 4:20 PM, PG Doc comments form wrote:
>>> Maybe I am misunderstanding the concept here but url = '/index.html' doesn't
>>> have any effect on this? If that's the case I would suggest either removing
>>> it from the first query or adding it to the second query.
>
>> You're correct, the url = '/index.html' does not affect if the partial
>> index is used in the example.
>
>> Based on how the example is set up, I'd propose using the "url"
>> parameter in both examples. I've attached a patch that does this, with
>> some additional wording around the examples.
>
> Yeah, this seems unnecessarily confusing. I tweaked your extra wording
> a bit --- I didn't like referring to the index as covering a range,
> because it's really excluding a range not including one.
You're right, that makes sense.
> Pushed.
Thanks!
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Westermann (DWE) | 2019-04-04 08:24:20 | Supported versions missing at the top of the page |
Previous Message | Tom Lane | 2019-04-03 22:30:52 | Re: Clarity in partial index example. |