Re: Clarity in partial index example.
"Jonathan S. Katz" <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.documentation |
|---|---|
| Message-ID | <[email protected]> |
On 4/3/19 6:30 PM, Tom Lane wrote: > "Jonathan S. Katz" <[email protected]> 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
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE+oS2la8r95ogZD/x8QSccp8cZScFAlylNFMACgkQ8QSccp8c ZSf4+Q//c1sca6uSDneL6e/sadro3TYJVcRFQ1B+x6TaTnO5rXbF6VlJbRfksZ47 5jinEyv3sTiP4jVCjm6sSnYbRAqFJqWuVk779522FcJar9Ht83LfUnJr+kRi4J2R 8j/fvgAfjHnLqxiB/GMqUxNDfES5idTTn+K8if2WUujVYrgDRcG8DCvOHqVSTH5D E1xMQs1aItH/i/ewa7mWPaMH2Sl4l91aCAOQ/EWzlxvyjkmw8hhSE8RrfdfRfjFp K/VV3egmeRmvKoiFQ3RLp7mLQbCSmpUzG0QLNbKOydhxfI6mUV9M00ocNwmejeCE CEDLe7xvo5GpfU1APHs4xP/tF9mdZfQtzq28NvaLQL9jswqn8kFk7uNRoiozmo2G xnQf/JI/bnnuElvG7IXQBxZGXuvLugDa+xwXQIYLItZilIdIwbU6DTjElS7EDGlI FNPq+oenbVuqS6MpFLQ1EXzk2gsenJ+wpNAWyUT5dMxEQre3wnWWPXGkzxz8jlf7 XBy8e3Cci7nTTMCahd+8rWnBllokOLYBDxRnkSOLMXRnPhzH9WNEpx7zs7zgaBBy DKxH0d0knbTq9Y0l2NyWIWANn1Qfk+tKgCC5idtn0KOqSSBVr5FeCpsSAIR/SN7D X0Q+MoXA2b0wPcot5HCQT64goYddDPhgziSQCHdcUgqHOKjM4AU= =3/Xh -----END PGP SIGNATURE-----