| From: | Erik Wienhold <ewie(at)ewie(dot)name> |
|---|---|
| To: | evasquezg97(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Error in Example |
| Date: | 2023-09-01 15:16:52 |
| Message-ID: | 2000743697.23098.1693581412642@office.mailbox.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 31/08/2023 01:29 CEST PG Doc comments form <noreply(at)postgresql(dot)org> wrote:
> Page: https://www.postgresql.org/docs/15/indexes-partial.html
> Description:
>
> The IP addresses used to exemplify which one will be covered by the partial
> index are inverted.
No, the example is correct. It's about only indexing addresses outside some
hypothetical organization's subnet 192.168.100.0/24. Notice that the index
predicate is negated.
Of course the predicate could be written without inverting the range:
WHERE (client_ip <= inet '192.168.100.0' OR
client_ip >= inet '192.168.100.255')
--
Erik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2023-09-05 09:36:45 | Clarification of deadlock possibilities in section 13.3.5. Advisory Locks |
| Previous Message | PG Doc comments form | 2023-08-30 23:29:56 | Error in Example |