diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2006-06-05 20:56:33 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2006-06-05 20:56:33 +0000 |
commit | 7868590c61fff0def9e46a59cad0890ecbecfe7f (patch) | |
tree | 4c65a355631fa2eb06c3d1e8daaf16767dcddbb3 /src/tutorial/beard.c | |
parent | b7af62e4a9a13be9857be9778f8114e8172924fe (diff) | |
download | postgresql-7868590c61fff0def9e46a59cad0890ecbecfe7f.tar.gz postgresql-7868590c61fff0def9e46a59cad0890ecbecfe7f.zip |
While making the seq_page_cost changes, I was struck by the fact that
cost_nonsequential_access() is really totally inappropriate for its only
remaining use, namely estimating I/O costs in cost_sort(). The routine
was designed on the assumption that disk caching might eliminate the need
for some re-reads on a random basis, but there's nothing very random in
that sense about sort's access pattern --- it'll always be picking up the
oldest outputs. If we had a good fix on the effective cache size we
might consider charging zero for I/O unless the sort temp file size
exceeds it, but that's probably putting much too much faith in the
parameter. Instead just drop the logic in favor of a fixed compromise
between seq_page_cost and random_page_cost per page of sort I/O.
Diffstat (limited to 'src/tutorial/beard.c')
0 files changed, 0 insertions, 0 deletions