Skip to content

Visually highlight the warning about using $min xor $max #2221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Visually highlight the warning about using $min xor $max #2221

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions source/includes/fact-query-min-max.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,9 @@ should avoid normal query planning. Instead they construct an index scan where
the index bounds are explicitly specified by the values given in
:operator:`min` and :operator:`max`.

If one of the two boundaries is not specified, then the query plan will be
an index scan that is unbounded on one side. This may degrade performance
compared to a query containing neither operator, or one that uses both
operators to more tightly constrain the index scan.
.. warning::

If one of the two boundaries is not specified, then the query plan will be
an index scan that is unbounded on one side. This may degrade performance
compared to a query containing neither operator, or one that uses both
operators to more tightly constrain the index scan.