database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-31 17:02:12 +03:00
Code Activity

Startup is actually start-up.

Browse Source
This commit is contained in:
Bruce Momjian
2000-08-29 20:02:09 +00:00
parent 883d1cc1cc
commit 67cd018e77
18 changed files with 82 additions and 82 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/ref/explain.sgml
View File

@@ -1,5 +1,5 @@
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/explain.sgml,v 1.9 2000/02/15 23:37:49 tgl Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/ref/explain.sgml,v 1.10 2000/08/29 20:02:09 momjian Exp $
Postgres documentation
-->
@@ -114,10 +114,10 @@ EXPLAIN
The most critical part of the display is the estimated query execution
cost, which is the planner's guess at how long it will take to run the
query (measured in units of disk page fetches). Actually two numbers
are shown: the startup time before the first tuple can be returned, and
are shown: the start-up time before the first tuple can be returned, and
the total time to return all the tuples. For most queries the total time
is what matters, but in contexts such as an EXISTS sub-query the planner
will choose the smallest startup time instead of the smallest total time
will choose the smallest start-up time instead of the smallest total time
(since the executor will stop after getting one tuple, anyway).
Also, if you limit the number of tuples to return with a LIMIT clause,
the planner makes an appropriate interpolation between the endpoint