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
56913735
Commit
56913735
authored
Apr 15, 2008
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Done:
> * -Allow administrators to safely terminate individual sessions either
parent
18b286f3
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
21 deletions
+4
-21
doc/TODO
doc/TODO
+2
-11
doc/src/FAQ/TODO.html
doc/src/FAQ/TODO.html
+2
-10
No files found.
doc/TODO
View file @
56913735
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated:
Mon Apr 14 09:33:40
EDT 2008
Last updated:
Tue Apr 15 09:55:33
EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
...
...
@@ -20,17 +20,8 @@ http://developer.postgresql.org.
Administration
==============
* Allow administrators to safely terminate individual sessions either
*
-
Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
Lock table corruption following SIGTERM of an individual backend
has been reported in 8.0. A possible cause was fixed in 8.1, but
it is unknown whether other problems exist. This item mostly
requires additional testing rather than of writing any new code.
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php
http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php
* Check for unreferenced table files created by transactions that were
in-progress when the server terminated abruptly
...
...
doc/src/FAQ/TODO.html
View file @
56913735
...
...
@@ -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:bruce@momjian.us"
>
bruce@momjian.us
</a>
)
<br/>
Last updated:
Mon Apr 14 09:33:40
EDT 2008
Last updated:
Tue Apr 15 09:55:33
EDT 2008
</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>
.
...
...
@@ -26,16 +26,8 @@ first. There is also a developer's wiki at<br/>
<h1><a
name=
"section_2"
>
Administration
</a></h1>
<ul>
<li>
Allow administrators to safely terminate individual sessions either
<li>
-
<em>
Allow administrators to safely terminate individual sessions either
</em>
via an SQL function or SIGTERM
<p>
Lock table corruption following SIGTERM of an individual backend
has been reported in 8.0. A possible cause was fixed in 8.1, but
it is unknown whether other problems exist. This item mostly
requires additional testing rather than of writing any new code.
</p>
<p>
<a
href=
"http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php"
>
http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php
</a>
<a
href=
"http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php"
>
http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php
</a>
</p>
</li><li>
Check for unreferenced table files created by transactions that were
in-progress when the server terminated abruptly
<p>
<a
href=
"http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php"
>
http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php
</a>
...
...
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