mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-12-03 08:00:21 +08:00
Code Issues Packages Projects Releases Wiki Activity

Move INDEX inheritance out into a separate section:

Browse Source 
< * Allow inherited tables to inherit index, UNIQUE constraint, and primary
<   key, foreign key
< * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
<   inherited table:  INSERT INTO inherit_table (unique_index_col) VALUES
<   (dup) should fail
<
<   The main difficulty with this item is the problem of creating an index
<   that can span more than one table.
<
< * Allow SELECT ... FOR UPDATE on inherited tables
> * Inheritance
>
> 	o Allow inherited tables to inherit indexes, UNIQUE constraints,
> 	  and primary/foreign keys
> 	o Honor UNIQUE INDEX on base column in INSERTs/UPDATEs
> 	  on inherited table, e.g.  INSERT INTO inherit_table
> 	  (unique_index_col) VALUES (dup) should fail
>
> 	  The main difficulty with this item is the problem of
> 	  creating an index that can span multiple tables.
>
> 	o Allow SELECT ... FOR UPDATE on inherited tables
>
>
>
This commit is contained in:
Bruce Momjian 2007-01-06 20:00:10 +00:00
parent 9cfcfd7c22
commit bd87cd5ffb
2 changed files with 30 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Sat Jan 6 14:41:18 EST 2007 Last updated: Sat Jan 6 14:59:54 EST 2007
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.
@ -855,16 +855,6 @@ Dependency Checking
Indexes Indexes
======= =======
* Allow inherited tables to inherit index, UNIQUE constraint, and primary
key, foreign key
* UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
inherited table: INSERT INTO inherit_table (unique_index_col) VALUES
(dup) should fail
The main difficulty with this item is the problem of creating an index
that can span more than one table.
* Allow SELECT ... FOR UPDATE on inherited tables
* Add UNIQUE capability to non-btree indexes * Add UNIQUE capability to non-btree indexes
* Prevent index uniqueness checks when UPDATE does not modify the column * Prevent index uniqueness checks when UPDATE does not modify the column
@ -904,12 +894,27 @@ Indexes
This is difficult because it requires datatype-specific knowledge. This is difficult because it requires datatype-specific knowledge.
* Inheritance
o Allow inherited tables to inherit indexes, UNIQUE constraints,
and primary/foreign keys
o Honor UNIQUE INDEX on base column in INSERTs/UPDATEs
on inherited table, e.g. INSERT INTO inherit_table
(unique_index_col) VALUES (dup) should fail
The main difficulty with this item is the problem of
creating an index that can span multiple tables.
o Allow SELECT ... FOR UPDATE on inherited tables
* GIST * GIST
o Add more GIST index support for geometric data types o Add more GIST index support for geometric data types
o Allow GIST indexes to create certain complex index types, like o Allow GIST indexes to create certain complex index types, like
digital trees (see Aoki) digital trees (see Aoki)
* Hash * Hash
o Pack hash index buckets onto disk pages more efficiently o Pack hash index buckets onto disk pages more efficiently

25
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: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: Sat Jan 6 14:41:18 EST 2007 Last updated: Sat Jan 6 14:59:54 EST 2007
</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>.
@ -776,16 +776,7 @@ first.
<h1><a name="section_12">Indexes</a></h1> <h1><a name="section_12">Indexes</a></h1>
<ul> <ul>
<li>Allow inherited tables to inherit index, UNIQUE constraint, and primary <li>Add UNIQUE capability to non-btree indexes
key, foreign key
</li><li>UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
inherited table: INSERT INTO inherit_table (unique_index_col) VALUES
(dup) should fail
<p> The main difficulty with this item is the problem of creating an index
that can span more than one table.
</p>
</li><li>Allow SELECT ... FOR UPDATE on inherited tables
</li><li>Add UNIQUE capability to non-btree indexes
</li><li>Prevent index uniqueness checks when UPDATE does not modify the column </li><li>Prevent index uniqueness checks when UPDATE does not modify the column
<p> Uniqueness (index) checks are done when updating a column even if the <p> Uniqueness (index) checks are done when updating a column even if the
column is not modified by the UPDATE. column is not modified by the UPDATE.
@ -818,6 +809,18 @@ first.
several rows as a single index entry several rows as a single index entry
<p> This is difficult because it requires datatype-specific knowledge. <p> This is difficult because it requires datatype-specific knowledge.
</p> </p>
</li><li>Inheritance
<ul>
<li>Allow inherited tables to inherit indexes, UNIQUE constraints,
and primary/foreign keys
</li><li>Honor UNIQUE INDEX on base column in INSERTs/UPDATEs
on inherited table, e.g. INSERT INTO inherit_table
(unique_index_col) VALUES (dup) should fail
<p> The main difficulty with this item is the problem of
creating an index that can span multiple tables.
</p>
</li><li>Allow SELECT ... FOR UPDATE on inherited tables
</li></ul>
</li><li>GIST </li><li>GIST
<ul> <ul>
<li>Add more GIST index support for geometric data types <li>Add more GIST index support for geometric data types