diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2000-02-21 01:13:04 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2000-02-21 01:13:04 +0000 |
commit | be05edd81296c7ec419b9af5a05460917a180b48 (patch) | |
tree | fe663eba2ea82248cc05e363041b4a622124b25c /src/backend/utils/adt/int.c | |
parent | 07c495f5d86b0cc5573dd0993cdd4069b2c893ca (diff) | |
download | postgresql-be05edd81296c7ec419b9af5a05460917a180b48.tar.gz postgresql-be05edd81296c7ec419b9af5a05460917a180b48.zip |
Tweak planner to use OFFSET+LIMIT, not just LIMIT, as estimate of the
portion of the query result that will be retrieved. As far as I could
tell, the consensus was that we should let the planner do the best it
can with a LIMIT query, and require the user to add ORDER BY if he
wants consistent results from different LIMIT values.
Diffstat (limited to 'src/backend/utils/adt/int.c')
0 files changed, 0 insertions, 0 deletions