|
10 | 10 | alink="#0000ff"> |
11 | 11 | <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
12 | 12 |
|
13 | | -<P>Last updated: Tue Nov 22 10:21:51 EST 2005</P> |
| 13 | +<P>Last updated: Tue Nov 22 10:31:18 EST 2005</P> |
14 | 14 |
|
15 | 15 | <P>Current maintainer: Bruce Momjian (<Ahref= |
16 | 16 | "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>) |
@@ -272,7 +272,7 @@ <H3 id="item1.8">1.8) How do I submit a bug report?</H3> |
272 | 272 | </li> |
273 | 273 | <li>The bug is new. The following might happen: |
274 | 274 | <ul> |
275 | | -<li>A patchhas been created and will be included in the next major |
| 275 | +<li>A patchis created and will be included in the next major |
276 | 276 | or minor release</li> |
277 | 277 | <li>The bug cannot be fixed immediately and is added |
278 | 278 | to the<Ahref="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A> |
@@ -312,10 +312,11 @@ <H3 id="item1.9">1.9) How do I find out about known bugs or |
312 | 312 | <Ahref="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A> |
313 | 313 | list up-to-date. In practice, bugs don't last very long in the |
314 | 314 | software, and bugs that affect a large number of users are fixed |
315 | | - rapidly. The only single place to find all changes, improvements, |
316 | | - and fixes in a PostgreSQL release is to read our CVS logs messages. |
317 | | - Even the release notes do not contain every change made to the |
318 | | - software.</P> |
| 315 | + rapidly. The only place to find all changes, improvements, and |
| 316 | + fixes in a PostgreSQL release is to read the |
| 317 | +<ahref="http://www.postgresql.org/developer/sourcecode/">CVS</a> |
| 318 | + log messages. Even the release notes do not list every change |
| 319 | + made to the software.</P> |
319 | 320 |
|
320 | 321 | <H3id="item1.10">1.10) What documentation is available?</H3> |
321 | 322 |
|
|