From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
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:30:52 |
Message-ID: | 12858.1554330652@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
"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.
Pushed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2019-04-03 22:31:47 | Re: Clarity in partial index example. |
Previous Message | Jonathan S. Katz | 2019-04-03 22:00:18 | Re: Clarity in partial index example. |