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

Commitbaf4e18

Browse files
committed
Update wording, query -> statement:
< * %Allow pooled connections to list all prepared queries> * %Allow pooled connections to list all prepared statements28c28< the queries prepared in the current session.> the statements prepared in the current session.143c143< o Allow a warm standby system to also allow read-only queries> o Allow a warm standby system to also allow read-only statements404c404< * Add GUC to issue notice about queries that use unjoined tables> * Add GUC to issue notice about statements that use unjoined tables490c490< Another idea would be to allow actual SELECT queries in a COPY.> Another idea would be to allow actual SELECT statements in a COPY.554c554< o Allow function argument names to be queries from PL/PgSQL> o Allow function argument names to be statements from PL/PgSQL591c591< o Improve psql's handling of multi-line queries> o Improve psql's handling of multi-line statements< Currently, while \e saves a single query as one entry, interactive< queries are saved one line at a time. Ideally all queries> Currently, while \e saves a single statement as one entry, interactive> statements are saved one line at a time. Ideally all statements665c665< o Allow query results to be automatically batched to the client> o Allow statement results to be automatically batched to the client667c667< Currently, all query results are transfered to the libpq> Currently, all statement results are transfered to the libpq672c672< One complexity is that a query like SELECT 1/col could error> One complexity is that a statement like SELECT 1/col could error739c739< * Allow queries across databases or servers with transaction> * Allow statements across databases or servers with transaction< inheritance, allow it to work for UPDATE and DELETE queries, and allow< it to be used for all queries with little performance impact> inheritance, allow it to work for UPDATE and DELETE statements, and allow> it to be used for all statements with little performance impact876c876< * Consider automatic caching of queries at various levels:> * Consider automatic caching of statements at various levels:947c947< a single session using multiple threads to execute a query faster.> a single session using multiple threads to execute a statement faster.1025c1025< * Log queries where the optimizer row estimates were dramatically> * Log statements where the optimizer row estimates were dramatically1146c1146< of result sets using new query protocol> of result sets using new statement protocol
1 parentcb4ea99 commitbaf4e18

File tree

2 files changed

+40
-40
lines changed

2 files changed

+40
-40
lines changed

‎doc/TODO

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
PostgreSQL TODO List
33
====================
44
Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated:Sat Dec10 21:16:26 EST 2005
5+
Last updated:Mon Dec12 08:36:28 EST 2005
66

77
The most recent version of this document can be viewed at
88
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -22,10 +22,10 @@ Administration
2222

2323
* %Remove behavior of postmaster -o after making postmaster/postgres
2424
flags unique
25-
* %Allow pooled connections to list all preparedqueries
25+
* %Allow pooled connections to list all preparedstatements
2626

2727
This would allow an application inheriting a pooled connection to know
28-
thequeries prepared in the current session.
28+
thestatements prepared in the current session.
2929

3030
* Allow major upgrades without dump/reload, perhaps using pg_upgrade
3131
[pg_upgrade]
@@ -140,7 +140,7 @@ Administration
140140

141141
o %Create dump tool for write-ahead logs for use in determining
142142
transaction id for point-in-time recovery
143-
o Allow a warm standby system to also allow read-onlyqueries
143+
o Allow a warm standby system to also allow read-onlystatements
144144
[pitr]
145145

146146
This is useful for checking PITR recovery.
@@ -401,7 +401,7 @@ SQL Commands
401401
is for this to be a protocol-only feature. Another approach is to
402402
notify the protocol when a RESET CONNECTION command is used.
403403

404-
* Add GUC to issue notice aboutqueries that use unjoined tables
404+
* Add GUC to issue notice aboutstatements that use unjoined tables
405405
* Allow EXPLAIN to identify tables that were skipped because of
406406
constraint_exclusion
407407
* Allow EXPLAIN output to be more easily processed by scripts
@@ -487,7 +487,7 @@ SQL Commands
487487

488488
o Allow COPY to output from views
489489

490-
Another idea would be to allow actual SELECTqueries in a COPY.
490+
Another idea would be to allow actual SELECTstatements in a COPY.
491491

492492

493493
* GRANT/REVOKE
@@ -551,7 +551,7 @@ SQL Commands
551551
o Add table function support to pltcl, plpython
552552
o Add capability to create and call PROCEDURES
553553
o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[]
554-
o Allow function argument names to bequeries from PL/PgSQL
554+
o Allow function argument names to bestatements from PL/PgSQL
555555
o Add MOVE to PL/pgSQL
556556
o Add support for polymorphic arguments and return types to
557557
languages other than PL/PgSQL
@@ -588,10 +588,10 @@ Clients
588588
o Allow psql \pset boolean variables to set to fixed values, rather
589589
than toggle
590590
o Consistently display privilege information for all objects in psql
591-
o Improve psql's handling of multi-linequeries
591+
o Improve psql's handling of multi-linestatements
592592

593-
Currently, while \e saves a singlequery as one entry, interactive
594-
queries are saved one line at a time. Ideally allqueries
593+
Currently, while \e saves a singlestatement as one entry, interactive
594+
statements are saved one line at a time. Ideally allstatements
595595
whould be saved like \e does.
596596

597597
o Allow multi-line column values to align in the proper columns
@@ -662,14 +662,14 @@ libpq
662662
PQfnumber() should never have been doing lowercasing, but
663663
historically it has so we need a way to prevent it
664664

665-
o Allowquery results to be automatically batched to the client
665+
o Allowstatement results to be automatically batched to the client
666666

667-
Currently, allquery results are transfered to the libpq
667+
Currently, allstatement results are transfered to the libpq
668668
client before libpq makes the results available to the
669669
application. This feature would allow the application to make
670670
use of the first result rows while the rest are transfered, or
671671
held on the server waiting for them to be requested by libpq.
672-
One complexity is that aquery like SELECT 1/col could error
672+
One complexity is that astatement like SELECT 1/col could error
673673
out mid-way through the result set.
674674

675675

@@ -736,7 +736,7 @@ Exotic Features
736736
* Allow plug-in modules to emulate features from other databases
737737
* SQL*Net listener that makes PostgreSQL appear as an Oracle database
738738
to clients
739-
* Allowqueries across databases or servers with transaction
739+
* Allowstatements across databases or servers with transaction
740740
semantics
741741

742742
This can be done using dblink and two-phase commit.
@@ -784,8 +784,8 @@ Indexes
784784
* Add fillfactor to control reserved free space during index creation
785785
* Allow the creation of indexes with mixed ascending/descending specifiers
786786
* Allow constraint_exclusion to work for UNIONs like it does for
787-
inheritance, allow it to work for UPDATE and DELETEqueries, and allow
788-
it to be used for allqueries with little performance impact
787+
inheritance, allow it to work for UPDATE and DELETEstatements, and allow
788+
it to be used for allstatements with little performance impact
789789
* Allow CREATE INDEX to take an additional parameter for use with
790790
special index types
791791
* Consider compressing indexes by storing key values duplicated in
@@ -873,7 +873,7 @@ Cache Usage
873873
accessed bitmaps would have to be stored in shared memory. One 8k
874874
page of bitmaps could track 512MB of heap pages.
875875

876-
* Consider automatic caching ofqueries at various levels:
876+
* Consider automatic caching ofstatements at various levels:
877877

878878
o Parsed query tree
879879
o Query execute plan
@@ -944,7 +944,7 @@ Startup Time Improvements
944944
operating systems have trivial process creation time compared to
945945
database startup overhead, but a few operating systems (WIn32,
946946
Solaris) might benefit from threading. Also explore the idea of
947-
a single session using multiple threads to execute aquery faster.
947+
a single session using multiple threads to execute astatement faster.
948948

949949
* Add connection pooling
950950

@@ -1022,7 +1022,7 @@ Optimizer / Executor
10221022
This would be beneficial when there are few distinct values. This is
10231023
already used by GROUP BY.
10241024

1025-
* Logqueries where the optimizer row estimates were dramatically
1025+
* Logstatements where the optimizer row estimates were dramatically
10261026
different from the number of rows actually found?
10271027

10281028

@@ -1143,7 +1143,7 @@ Source Code
11431143
o Add decoded type, length, precision
11441144
o Use compression?
11451145
o Update clients to use data types, typmod, schema.table.column names
1146-
of result sets using newquery protocol
1146+
of result sets using newstatement protocol
11471147

11481148

11491149
---------------------------------------------------------------------------

‎doc/src/FAQ/TODO.html

Lines changed: 20 additions & 20 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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
11-
Last updated:Sat Dec10 21:16:26 EST 2005
11+
Last updated:Mon Dec12 08:36:28 EST 2005
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>.
@@ -27,9 +27,9 @@ <h1><a name="section_2">Administration</a></h1>
2727
<ul>
2828
<li>%Remove behavior of postmaster -o after making postmaster/postgres
2929
flags unique
30-
</li><li>%Allow pooled connections to list all preparedqueries
30+
</li><li>%Allow pooled connections to list all preparedstatements
3131
<p> This would allow an application inheriting a pooled connection to know
32-
thequeries prepared in the current session.
32+
thestatements prepared in the current session.
3333
</p>
3434
</li><li>Allow major upgrades without dump/reload, perhaps using pg_upgrade
3535
[<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?pg_upgrade">pg_upgrade</a>]
@@ -130,7 +130,7 @@ <h1><a name="section_2">Administration</a></h1>
130130
</p>
131131
</li><li>%Create dump tool for write-ahead logs for use in determining
132132
transaction id for point-in-time recovery
133-
</li><li>Allow a warm standby system to also allow read-onlyqueries
133+
</li><li>Allow a warm standby system to also allow read-onlystatements
134134
[<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
135135
<p> This is useful for checking PITR recovery.
136136
</p>
@@ -368,7 +368,7 @@ <h1><a name="section_8">SQL Commands</a></h1>
368368
is for this to be a protocol-only feature. Another approach is to
369369
notify the protocol when a RESET CONNECTION command is used.
370370
</p>
371-
</li><li>Add GUC to issue notice aboutqueries that use unjoined tables
371+
</li><li>Add GUC to issue notice aboutstatements that use unjoined tables
372372
</li><li>Allow EXPLAIN to identify tables that were skipped because of
373373
constraint_exclusion
374374
</li><li>Allow EXPLAIN output to be more easily processed by scripts
@@ -443,7 +443,7 @@ <h1><a name="section_8">SQL Commands</a></h1>
443443
currently allowed.
444444
</p>
445445
</li><li>Allow COPY to output from views
446-
<p> Another idea would be to allow actual SELECTqueries in a COPY.
446+
<p> Another idea would be to allow actual SELECTstatements in a COPY.
447447
</p>
448448
</li></ul>
449449
</li><li>GRANT/REVOKE
@@ -502,7 +502,7 @@ <h1><a name="section_8">SQL Commands</a></h1>
502502
</li><li>Add table function support to pltcl, plpython
503503
</li><li>Add capability to create and call PROCEDURES
504504
</li><li>Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]
505-
</li><li>Allow function argument names to bequeries from PL/PgSQL
505+
</li><li>Allow function argument names to bestatements from PL/PgSQL
506506
</li><li>Add MOVE to PL/pgSQL
507507
</li><li>Add support for polymorphic arguments and return types to
508508
languages other than PL/PgSQL
@@ -536,9 +536,9 @@ <h1><a name="section_9">Clients</a></h1>
536536
</li><li>Allow psql \pset boolean variables to set to fixed values, rather
537537
than toggle
538538
</li><li>Consistently display privilege information for all objects in psql
539-
</li><li>Improve psql's handling of multi-linequeries
540-
<p> Currently, while \e saves a singlequery as one entry, interactive
541-
queries are saved one line at a time. Ideally allqueries
539+
</li><li>Improve psql's handling of multi-linestatements
540+
<p> Currently, while \e saves a singlestatement as one entry, interactive
541+
statements are saved one line at a time. Ideally allstatements
542542
whould be saved like \e does.
543543
</p>
544544
</li><li>Allow multi-line column values to align in the proper columns
@@ -604,13 +604,13 @@ <h1><a name="section_9">Clients</a></h1>
604604
<p> PQfnumber() should never have been doing lowercasing, but
605605
historically it has so we need a way to prevent it
606606
</p>
607-
</li><li>Allowquery results to be automatically batched to the client
608-
<p> Currently, allquery results are transfered to the libpq
607+
</li><li>Allowstatement results to be automatically batched to the client
608+
<p> Currently, allstatement results are transfered to the libpq
609609
client before libpq makes the results available to the
610610
application. This feature would allow the application to make
611611
use of the first result rows while the rest are transfered, or
612612
held on the server waiting for them to be requested by libpq.
613-
One complexity is that aquery like SELECT 1/col could error
613+
One complexity is that astatement like SELECT 1/col could error
614614
out mid-way through the result set.
615615
</p>
616616
</li></ul>
@@ -671,7 +671,7 @@ <h1><a name="section_12">Exotic Features</a></h1>
671671
</li><li>Allow plug-in modules to emulate features from other databases
672672
</li><li>SQL*Net listener that makes PostgreSQL appear as an Oracle database
673673
to clients
674-
</li><li>Allowqueries across databases or servers with transaction
674+
</li><li>Allowstatements across databases or servers with transaction
675675
semantics
676676
<p> This can be done using dblink and two-phase commit.
677677
</p>
@@ -714,8 +714,8 @@ <h1><a name="section_13">Indexes</a></h1>
714714
</li><li>Add fillfactor to control reserved free space during index creation
715715
</li><li>Allow the creation of indexes with mixed ascending/descending specifiers
716716
</li><li>Allow constraint_exclusion to work for UNIONs like it does for
717-
inheritance, allow it to work for UPDATE and DELETEqueries, and allow
718-
it to be used for allqueries with little performance impact
717+
inheritance, allow it to work for UPDATE and DELETEstatements, and allow
718+
it to be used for allstatements with little performance impact
719719
</li><li>Allow CREATE INDEX to take an additional parameter for use with
720720
special index types
721721
</li><li>Consider compressing indexes by storing key values duplicated in
@@ -792,7 +792,7 @@ <h1><a name="section_15">Cache Usage</a></h1>
792792
accessed bitmaps would have to be stored in shared memory. One 8k
793793
page of bitmaps could track 512MB of heap pages.
794794
</p>
795-
</li><li>Consider automatic caching ofqueries at various levels:
795+
</li><li>Consider automatic caching ofstatements at various levels:
796796
<ul>
797797
<li>Parsed query tree
798798
</li><li>Query execute plan
@@ -855,7 +855,7 @@ <h1><a name="section_18">Startup Time Improvements</a></h1>
855855
operating systems have trivial process creation time compared to
856856
database startup overhead, but a few operating systems (WIn32,
857857
Solaris) might benefit from threading. Also explore the idea of
858-
a single session using multiple threads to execute aquery faster.
858+
a single session using multiple threads to execute astatement faster.
859859
</p>
860860
</li><li>Add connection pooling
861861
<p> It is unclear if this should be done inside the backend code or done
@@ -927,7 +927,7 @@ <h1><a name="section_20">Optimizer / Executor</a></h1>
927927
<p> This would be beneficial when there are few distinct values. This is
928928
already used by GROUP BY.
929929
</p>
930-
</li><li>Logqueries where the optimizer row estimates were dramatically
930+
</li><li>Logstatements where the optimizer row estimates were dramatically
931931
different from the number of rows actually found?
932932
</li></ul>
933933
<h1><aname="section_21">Miscellaneous Performance</a></h1>
@@ -1037,7 +1037,7 @@ <h1><a name="section_22">Source Code</a></h1>
10371037
</li><li>Add decoded type, length, precision
10381038
</li><li>Use compression?
10391039
</li><li>Update clients to use data types, typmod,<ahref="http://schema.table.column">schema.table.column</a>/ names
1040-
of result sets using newquery protocol
1040+
of result sets using newstatement protocol
10411041
</li></ul>
10421042
</li></ul>
10431043
<hr/>

0 commit comments

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