open-dsi
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Not done:

Browse Source 
< 	o -Allow an existing index to be marked as a table's primary key
> 	o Allow an existing index to be marked as a table's primary key
REL8_5_ALPHA1_BRANCH
Bruce Momjian 17 years ago
parent 3cab8bdf43
commit 7303b20964
2 changed files with 13 additions and 13 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 4
      doc/TODO
  2. 22
      doc/src/FAQ/TODO.html

4
doc/TODO
Unescape View File

@ -1,7 +1,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Tue Aug 19 12:39:00 EDT 2008 Last updated: Tue Aug 19 15:19:46 EDT 2008
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.
@ -848,7 +848,7 @@ SQL Commands
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php
o -Allow an existing index to be marked as a table's primary key o Allow an existing index to be marked as a table's primary key
http://archives.postgresql.org/pgsql-hackers/2008-04/msg00500.php http://archives.postgresql.org/pgsql-hackers/2008-04/msg00500.php

22
doc/src/FAQ/TODO.html
Unescape View File

@ -1,14 +1,14 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html>
<head> <head>
<title>PostgreSQL TODO List</title> <title>PostgreSQL TODO List</title>
<meta name="generator" content="HTML::TextToHTML v2.51"/> <meta name="generator" content="HTML::TextToHTML v2.25"/>
</head> </head>
<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:bruce@momjian.us">bruce@momjian.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
Last updated: Tue Aug 19 12:39:00 EDT 2008 Last updated: Tue Aug 19 15:19:46 EDT 2008
</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>.
@ -730,7 +730,7 @@ first. There is also a developer's wiki at<br/>
storage, and permanent id for every column? storage, and permanent id for every column?
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php</a> <p> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php</a>
</p> </p>
</li><li>-<em>Allow an existing index to be marked as a table's primary key</em> </li><li>Allow an existing index to be marked as a table's primary key
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-04/msg00500.php">http://archives.postgresql.org/pgsql-hackers/2008-04/msg00500.php</a> <p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-04/msg00500.php">http://archives.postgresql.org/pgsql-hackers/2008-04/msg00500.php</a>
</p> </p>
</li></ul> </li></ul>
@ -996,7 +996,7 @@ first. There is also a developer's wiki at<br/>
widths. Perhaps the word wrapping could use the same widths. Perhaps the word wrapping could use the same
algorithm documented in the W3C specification. algorithm documented in the W3C specification.
<a href="http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php">http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php</a> <a href="http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php">http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php</a>
<a href="http://www.w3.org/TR/CSS21/tables.html#auto-table-layout">http://www.w3.org/TR/CSS21/tables.html#auto-table-layout</a> <a href="http://www.w3.org/TR/CSS21/tables.html<strong>auto-table-layout">http://www.w3.org/TR/CSS21/tables.html</strong>auto-table-layout</a>
<li>Add "auto" expanded mode that outputs in expanded format if <li>Add "auto" expanded mode that outputs in expanded format if
"wrapped" mode can't wrap the output to the screen width "wrapped" mode can't wrap the output to the screen width
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-05/msg00417.php">http://archives.postgresql.org/pgsql-hackers/2008-05/msg00417.php</a> <p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-05/msg00417.php">http://archives.postgresql.org/pgsql-hackers/2008-05/msg00417.php</a>
@ -1102,8 +1102,8 @@ first. There is also a developer's wiki at<br/>
</p> </p>
</li></ul> </li></ul>
</li></ul> </li></ul>
<h1><a name="section_11">Triggers</a></h1> </p><h1><a name="section_11">Triggers</a></h1>
</p>
<ul> <ul>
<li>Add deferred trigger queue file <li>Add deferred trigger queue file
<p> Right now all deferred trigger information is stored in backend <p> Right now all deferred trigger information is stored in backend
@ -1326,7 +1326,7 @@ first. There is also a developer's wiki at<br/>
<a href="http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php">http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php</a> <a href="http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php">http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php</a>
</p> </p>
</li><li>Consider automatic caching of statements at various levels: </li><li>Consider automatic caching of statements at various levels:
Parsed query tree, query execution plan, query results parsed query tree, query execution plan, query results
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php">http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php</a> <p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php">http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php</a>
</p> </p>
</li><li>Consider increasing internal areas when shared buffers is increased </li><li>Consider increasing internal areas when shared buffers is increased
@ -1842,7 +1842,7 @@ first. There is also a developer's wiki at<br/>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php</a> <p> <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php</a>
</p> </p>
</li></ul> </li></ul>
<h1><a name="section_25">Features We Do _Not_ Want</a></h1> <h1><a name="section_25">Features We Do <u>Not</u> Want</a></h1>
<ul> <ul>
<li>All backends running as threads in a single process (not wanted) <li>All backends running as threads in a single process (not wanted)

Write Preview
Loading…
Cancel
Save