Skip to content

P
Postgres FD Implementation
Commit ea3db8f7 authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Update item: 

< * Improve deadlock detection when deleting items from shared buffers
> * Improve deadlock detection when a page cleaning lock conflicts
>   with a shared buffer that is pinned
parent b07e5485
Show whitespace changes
Inline Side-by-side
Showing with 6 additions and 4 deletions
doc/TODO
View file @ ea3db8f7
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Thu Jan 31 10:05:01 EST 2008 Last updated: Thu Jan 31 21:41:04 EST 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.
...@@ -1144,7 +1144,8 @@ Locking ...@@ -1144,7 +1144,8 @@ Locking
* Add idle_in_transaction_timeout GUC so locks are not held for long * Add idle_in_transaction_timeout GUC so locks are not held for long
periods of time periods of time
* Improve deadlock detection when deleting items from shared buffers * Improve deadlock detection when a page cleaning lock conflicts
with a shared buffer that is pinned
http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php
http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php
......
doc/src/FAQ/TODO.html
View file @ ea3db8f7
...@@ -8,7 +8,7 @@ ...@@ -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: Thu Jan 31 10:05:01 EST 2008 Last updated: Thu Jan 31 21:41:04 EST 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>.
...@@ -1018,7 +1018,8 @@ first. There is also a developer's wiki at<br/> ...@@ -1018,7 +1018,8 @@ first. There is also a developer's wiki at<br/>
</p> </p>
</li><li>Add idle_in_transaction_timeout GUC so locks are not held for long </li><li>Add idle_in_transaction_timeout GUC so locks are not held for long
periods of time periods of time
</li><li>Improve deadlock detection when deleting items from shared buffers </li><li>Improve deadlock detection when a page cleaning lock conflicts
with a shared buffer that is pinned
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php">http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php</a> <p> <a href="http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php">http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php</a> <a href="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php">http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php</a>
<a href="http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php">http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php</a> <a href="http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php">http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php</a>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment