sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-14 00:03:46 -04:00
Code Issues Projects Releases Wiki Activity

Update wording and cleanup for new items.

Browse Source
This commit is contained in:
Bruce Momjian 2005-11-22 15:31:23 +00:00
parent 5b352d8e12
commit b621efbbb8
2 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/FAQ
View File

@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL 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) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@ -212,8 +212,8 @@
+ Debugging information + Debugging information
+ Debugger backtrace output + Debugger backtrace output
* The bug is new. The following might happen: * The bug is new. The following might happen:
+ A patch has been created and will be included in the next + A patch is created and will be included in the next major or
major or minor release minor release
+ The bug cannot be fixed immediately and is added to the TODO + The bug cannot be fixed immediately and is added to the TODO
list list
@ -236,9 +236,9 @@
efficient to respond directly to email and keep the TODO list 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, 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 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 only place to find all changes, improvements, and fixes in a
PostgreSQL release is to read our CVS logs messages. Even the release PostgreSQL release is to read the CVS log messages. Even the release
notes do not contain every change made to the software. notes do not list every change made to the software.
1.10) What documentation is available? 1.10) What documentation is available?

13
doc/src/FAQ/FAQ.html
View File

@ -10,7 +10,7 @@
alink="#0000ff"> alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> <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= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>) "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
@ -272,7 +272,7 @@
</li> </li>
<li>The bug is new. The following might happen: <li>The bug is new. The following might happen:
<ul> <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> or minor release</li>
<li>The bug cannot be fixed immediately and is added <li>The bug cannot be fixed immediately and is added
to the <A href="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A> 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> <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 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 software, and bugs that affect a large number of users are fixed
rapidly. The only single place to find all changes, improvements, rapidly. The only place to find all changes, improvements, and
and fixes in a PostgreSQL release is to read our CVS logs messages. fixes in a PostgreSQL release is to read the
Even the release notes do not contain every change made to the <a href="http://www.postgresql.org/developer/sourcecode/">CVS</a>
software.</P> 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> <H3 id="item1.10">1.10) What documentation is available?</H3>