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

Done:

Browse Source 
> * -Implement shared row locks and use them in RI triggers
REL8_1_STABLE
Bruce Momjian 21 years ago
parent bedb78d386
commit daec16d0ba
2 changed files with 4 additions and 17 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. 11
      doc/TODO
  2. 10
      doc/src/FAQ/TODO.html

11
doc/TODO
Unescape View File

@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Mon Apr 25 11:35:24 EDT 2005
Last updated: Fri Apr 29 01:02:49 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -603,14 +603,7 @@ Referential Integrity
memory. This could exhaust memory for very large trigger queues.
This item involves dumping large queues into files.
* Implement dirty reads or shared row locks and use them in RI triggers
Adding shared locks requires recording the table/rows numbers in a
shared area, and this could potentially be a large amount of data.
One idea is to store the table/row numbers in a separate table and set
a bit on the row indicating looking in this new table is required to
find any shared row locks.
* -Implement shared row locks and use them in RI triggers
* Enforce referential integrity for system tables
* Change foreign key constraint for array -> element to mean element
in array (?)

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

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<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/>
Last updated: Mon Apr 25 11:35:24 EDT 2005
Last updated: Fri Apr 29 01:02:49 EDT 2005
</p>
<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>.
@ -557,13 +557,7 @@ first.
memory. This could exhaust memory for very large trigger queues.
This item involves dumping large queues into files.
</p>
</li><li>Implement dirty reads or shared row locks and use them in RI triggers
<p> Adding shared locks requires recording the table/rows numbers in a
shared area, and this could potentially be a large amount of data.
One idea is to store the table/row numbers in a separate table and set
a bit on the row indicating looking in this new table is required to
find any shared row locks.
</p>
</li><li>-Implement shared row locks and use them in RI triggers
</li><li>Enforce referential integrity for system tables
</li><li>Change foreign key constraint for array -&gt; element to mean element
in array (?)

Write Preview
Loading…
Cancel
Save