database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

Update wording:

Browse Source 
<
390d388
<
453c451
< 	  removed or have its heap and index files truncated.  One
> 	  be removed or have its heap and index files truncated.  One
< * Use a phantom command counter for nested subtransactions to reduce
<   per-tuple overhead
This commit is contained in:
Bruce Momjian
2005-09-16 16:46:09 +00:00
parent f4516f8732
commit 0296606f78
2 changed files with 4 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Fri Sep 16 07:23:51 EDT 2005 Last updated: Fri Sep 16 12:46:03 EDT 2005
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
@ -384,10 +384,8 @@ SQL Commands
o Allow CREATE TABLE AS to determine column lengths for complex o Allow CREATE TABLE AS to determine column lengths for complex
expressions like SELECT col1 || col2 expressions like SELECT col1 || col2
o Use more reliable method for CREATE DATABASE to get a consistent o Use more reliable method for CREATE DATABASE to get a consistent
copy of db? copy of db?
o Add ON COMMIT capability to CREATE TABLE AS ... SELECT o Add ON COMMIT capability to CREATE TABLE AS ... SELECT
@ -450,7 +448,7 @@ SQL Commands
o Allow COPY on a newly-created table to skip WAL logging o Allow COPY on a newly-created table to skip WAL logging
On crash recovery, the table involved in the COPY would On crash recovery, the table involved in the COPY would
removed or have its heap and index files truncated. One be removed or have its heap and index files truncated. One
issue is that no other backend should be able to add to issue is that no other backend should be able to add to
the table at the same time, which is something that is the table at the same time, which is something that is
currently allowed. currently allowed.
@ -990,8 +988,6 @@ Miscellaneous Performance
cmin/cmax pair and is stored in local memory. Another idea is to cmin/cmax pair and is stored in local memory. Another idea is to
store both cmin and cmax only in local memory. store both cmin and cmax only in local memory.
* Use a phantom command counter for nested subtransactions to reduce
per-tuple overhead
* Research storing disk pages with no alignment/padding * Research storing disk pages with no alignment/padding
Source Code Source Code

6
doc/src/FAQ/TODO.html
View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Fri Sep 16 07:23:51 EDT 2005 Last updated: Fri Sep 16 12:46:03 EDT 2005
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@ -408,7 +408,7 @@ first.
</li><li>%Have COPY return the number of rows loaded/unloaded? </li><li>%Have COPY return the number of rows loaded/unloaded?
</li><li>Allow COPY on a newly-created table to skip WAL logging </li><li>Allow COPY on a newly-created table to skip WAL logging
<p> On crash recovery, the table involved in the COPY would <p> On crash recovery, the table involved in the COPY would
removed or have its heap and index files truncated. One be removed or have its heap and index files truncated. One
issue is that no other backend should be able to add to issue is that no other backend should be able to add to
the table at the same time, which is something that is the table at the same time, which is something that is
currently allowed. currently allowed.
@ -895,8 +895,6 @@ first.
cmin/cmax pair and is stored in local memory. Another idea is to cmin/cmax pair and is stored in local memory. Another idea is to
store both cmin and cmax only in local memory. store both cmin and cmax only in local memory.
</p> </p>
</li><li>Use a phantom command counter for nested subtransactions to reduce
per-tuple overhead
</li><li>Research storing disk pages with no alignment/padding </li><li>Research storing disk pages with no alignment/padding
</li></ul> </li></ul>
<h1><a name="section_22">Source Code</a></h1> <h1><a name="section_22">Source Code</a></h1>