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

Commit62c0618

Browse files
committed
Remove completed items, and the last is unwanted:
< o Fix memory leak from exceptions<<http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php<< * Allow constraint_exclusion to work for UNIONs like it does for< inheritance, allow it to work for UPDATE and DELETE statements, and allow< it to be used for all statements with little performance impact<< * Add estimated_count(*) to return an estimate of COUNT(*)<< This would use the planner ANALYZE statistics to return an estimated< count.<http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php
1 parent9a54b76 commit62c0618

File tree

2 files changed

+2
-26
lines changed

2 files changed

+2
-26
lines changed

‎doc/TODO

Lines changed: 1 addition & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (bruce@momjian.us)
5-
Last updated:Wed Jan10 23:48:50 EST 2007
5+
Last updated:Sat Jan13 10:13:24 EST 2007
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -680,10 +680,6 @@ SQL Commands
680680

681681
http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
682682

683-
o Fix memory leak from exceptions
684-
685-
http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php
686-
687683
o Fix problems with RETURN NEXT on tables with
688684
dropped/added columns after function creation
689685

@@ -897,9 +893,6 @@ Indexes
897893
one column or expression indexes, perhaps using per-index statistics
898894
* -Allow the creation of indexes with mixed ascending/descending
899895
specifiers
900-
* Allow constraint_exclusion to work for UNIONs like it does for
901-
inheritance, allow it to work for UPDATE and DELETE statements, and allow
902-
it to be used for all statements with little performance impact
903896
* Consider compressing indexes by storing key values duplicated in
904897
several rows as a single index entry
905898

@@ -979,12 +972,6 @@ Cache Usage
979972
faster than a sequential scan it must avoid access to the heap
980973
to obtain tuple visibility information.
981974

982-
* Add estimated_count(*) to return an estimate of COUNT(*)
983-
984-
This would use the planner ANALYZE statistics to return an estimated
985-
count.
986-
http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php
987-
988975
* Allow data to be pulled directly from indexes
989976

990977
Currently indexes do not have enough tuple visibility information

‎doc/src/FAQ/TODO.html

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">
99
<h1><aname="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated:Wed Jan10 23:48:50 EST 2007
11+
Last updated:Sat Jan13 10:13:24 EST 2007
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -614,9 +614,6 @@ <h1><a name="section_8">SQL Commands</a></h1>
614614
</p>
615615
</li><li>Allow PL/RETURN to return row or record functions
616616
<p><ahref="http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php">http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php</a>
617-
</p>
618-
</li><li>Fix memory leak from exceptions
619-
<p><ahref="http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php">http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php</a>
620617
</p>
621618
</li><li>Fix problems with RETURN NEXT on tables with
622619
dropped/added columns after function creation
@@ -810,9 +807,6 @@ <h1><a name="section_12">Indexes</a></h1>
810807
one column or expression indexes, perhaps using per-index statistics
811808
</li><li>-<em>Allow the creation of indexes with mixed ascending/descending</em>
812809
specifiers
813-
</li><li>Allow constraint_exclusion to work for UNIONs like it does for
814-
inheritance, allow it to work for UPDATE and DELETE statements, and allow
815-
it to be used for all statements with little performance impact
816810
</li><li>Consider compressing indexes by storing key values duplicated in
817811
several rows as a single index entry
818812
<p> This is difficult because it requires datatype-specific knowledge.
@@ -879,11 +873,6 @@ <h1><a name="section_14">Cache Usage</a></h1>
879873
get a count directly from a unique index, but for this to be
880874
faster than a sequential scan it must avoid access to the heap
881875
to obtain tuple visibility information.
882-
</p>
883-
</li><li>Add estimated_count(*) to return an estimate of COUNT(*)
884-
<p> This would use the planner ANALYZE statistics to return an estimated
885-
count.
886-
<ahref="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php</a>
887876
</p>
888877
</li><li>Allow data to be pulled directly from indexes
889878
<p> Currently indexes do not have enough tuple visibility information

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp