diff options
| -rw-r--r-- | doc/FAQ | 12 | ||||
| -rw-r--r-- | doc/src/FAQ/FAQ.html | 13 |
2 files changed, 13 insertions, 12 deletions
@@ -1,7 +1,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL - Last updated: Tue Nov 22 10:21:51 EST 2005 + Last updated: Tue Nov 22 10:31:18 EST 2005 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) @@ -212,8 +212,8 @@ + Debugging information + Debugger backtrace output * The bug is new. The following might happen: - + A patch has been created and will be included in the next - major or minor release + + A patch is created and will be included in the next major or + minor release + The bug cannot be fixed immediately and is added to the TODO list @@ -236,9 +236,9 @@ efficient to respond directly to email and keep the TODO list up-to-date. In practice, bugs don't last very long in the software, and bugs that affect a large number of users are fixed rapidly. The - only single place to find all changes, improvements, and fixes in a - PostgreSQL release is to read our CVS logs messages. Even the release - notes do not contain every change made to the software. + only place to find all changes, improvements, and fixes in a + PostgreSQL release is to read the CVS log messages. Even the release + notes do not list every change made to the software. 1.10) What documentation is available? diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index 634286dc829..8bf6153c789 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -10,7 +10,7 @@ alink="#0000ff"> <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> - <P>Last updated: Tue Nov 22 10:21:51 EST 2005</P> + <P>Last updated: Tue Nov 22 10:31:18 EST 2005</P> <P>Current maintainer: Bruce Momjian (<A href= "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>) @@ -272,7 +272,7 @@ </li> <li>The bug is new. The following might happen: <ul> - <li>A patch has been created and will be included in the next major + <li>A patch is created and will be included in the next major or minor release</li> <li>The bug cannot be fixed immediately and is added to the <A href="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A> @@ -312,10 +312,11 @@ <A href="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A> list up-to-date. In practice, bugs don't last very long in the software, and bugs that affect a large number of users are fixed - rapidly. The only single place to find all changes, improvements, - and fixes in a PostgreSQL release is to read our CVS logs messages. - Even the release notes do not contain every change made to the - software.</P> + rapidly. The only place to find all changes, improvements, and + fixes in a PostgreSQL release is to read the + <a href="http://www.postgresql.org/developer/sourcecode/">CVS</a> + log messages. Even the release notes do not list every change + made to the software.</P> <H3 id="item1.10">1.10) What documentation is available?</H3> |