Skip to content

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

Add to item log_min_error_messages item: 

>   Another idea is to allow separate configuration files for each module,
>   or allow arbitrary SET commands to be passed to them.
parent 2fddd23b
Show whitespace changes
Inline Side-by-side
Showing with 6 additions and 2 deletions
doc/TODO
View file @ 87f00a46
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Wed Apr 26 22:41:35 EDT 2006 Last updated: Thu Apr 27 11:56:04 EDT 2006
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.
...@@ -54,6 +54,8 @@ Administration ...@@ -54,6 +54,8 @@ Administration
This would allow administrators to see more detailed information from This would allow administrators to see more detailed information from
specific sections of the backend, e.g. checkpoints, autovacuum, etc. specific sections of the backend, e.g. checkpoints, autovacuum, etc.
Another idea is to allow separate configuration files for each module,
or allow arbitrary SET commands to be passed to them.
* -Re-enable the GUC full_page_writes in 8.2 when reliability issues have * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have
been addressed been addressed
......
doc/src/FAQ/TODO.html
View file @ 87f00a46
...@@ -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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Wed Apr 26 22:41:35 EDT 2006 Last updated: Thu Apr 27 11:56:04 EDT 2006
</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>.
...@@ -55,6 +55,8 @@ first. ...@@ -55,6 +55,8 @@ first.
</li><li>Allow log_min_messages to be specified on a per-module basis </li><li>Allow log_min_messages to be specified on a per-module basis
<p> This would allow administrators to see more detailed information from <p> This would allow administrators to see more detailed information from
specific sections of the backend, e.g. checkpoints, autovacuum, etc. specific sections of the backend, e.g. checkpoints, autovacuum, etc.
Another idea is to allow separate configuration files for each module,
or allow arbitrary SET commands to be passed to them.
</p> </p>
</li><li>-<em>Re-enable the GUC full_page_writes in 8.2 when reliability issues have</em> </li><li>-<em>Re-enable the GUC full_page_writes in 8.2 when reliability issues have</em>
been addressed been addressed
......
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