Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit83b4ab5

Browse files
committed
Update a couple of obsolete comments.
1 parentbdacacd commit83b4ab5

File tree

1 file changed

+3
-9
lines changed

1 file changed

+3
-9
lines changed

‎src/backend/optimizer/path/costsize.c

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -34,15 +34,14 @@
3434
* Note that a relation's rows count (and, by extension, a Plan's plan_rows)
3535
* are set without regard to any LIMIT, so that this equation works properly.
3636
* (Also, these routines guarantee not to set the rows count to zero, so there
37-
* will be no zero divide.) RelOptInfos, Paths, and Plans themselves never
38-
* account for LIMIT.
37+
* will be no zero divide.) The LIMIT is applied as a separate Plan node.
3938
*
4039
*
4140
* Portions Copyright (c) 1996-2001, PostgreSQL Global Development Group
4241
* Portions Copyright (c) 1994, Regents of the University of California
4342
*
4443
* IDENTIFICATION
45-
* $Header: /cvsroot/pgsql/src/backend/optimizer/path/costsize.c,v 1.66 2001/01/24 19:42:57 momjian Exp $
44+
* $Header: /cvsroot/pgsql/src/backend/optimizer/path/costsize.c,v 1.67 2001/02/15 17:46:40 tgl Exp $
4645
*
4746
*-------------------------------------------------------------------------
4847
*/
@@ -96,15 +95,10 @@ static double page_size(double tuples, int width);
9695
* cost_seqscan
9796
* Determines and returns the cost of scanning a relation sequentially.
9897
*
99-
* If the relation is a temporary to be materialized from a query
100-
* embedded within a data field (determined by 'relid' containing an
101-
* attribute reference), then a predetermined constant is returned (we
102-
* have NO IDEA how big the result of a POSTQUEL procedure is going to be).
103-
*
10498
* Note: for historical reasons, this routine and the others in this module
10599
* use the passed result Path only to store their startup_cost and total_cost
106100
* results into. All the input data they need is passed as separate
107-
* parameters, even though much of it could be extracted from theresultPath.
101+
* parameters, even though much of it could be extracted from the Path.
108102
*/
109103
void
110104
cost_seqscan(Path*path,RelOptInfo*baserel)

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp