Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
daec16d0
Commit
daec16d0
authored
Apr 29, 2005
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Done:
> * -Implement shared row locks and use them in RI triggers
parent
bedb78d3
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
17 deletions
+4
-17
doc/TODO
doc/TODO
+2
-9
doc/src/FAQ/TODO.html
doc/src/FAQ/TODO.html
+2
-8
No files found.
doc/TODO
View file @
daec16d0
...
...
@@ -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 (?)
...
...
doc/src/FAQ/TODO.html
View file @
daec16d0
...
...
@@ -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 -
>
element to mean element
in array (?)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment