mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-03 08:00:21 +08:00
Update heading for upgrades.
This commit is contained in:
parent
0f9652848b
commit
4fc6aa4bc2
8
doc/FAQ
8
doc/FAQ
@ -1,7 +1,7 @@
|
||||
|
||||
Frequently Asked Questions (FAQ) for PostgreSQL
|
||||
|
||||
Last updated: Tue May 23 11:22:06 EDT 2006
|
||||
Last updated: Tue May 23 11:47:16 EDT 2006
|
||||
|
||||
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
||||
|
||||
@ -42,8 +42,7 @@
|
||||
3.3) How do I tune the database engine for better performance?
|
||||
3.4) What debugging features are available?
|
||||
3.5) Why do I get "Sorry, too many clients" when trying to connect?
|
||||
3.6) Why do I need to do a dump and restore to upgrade PostgreSQL
|
||||
releases?
|
||||
3.6 What should I do about upgrading PostgreSQL?
|
||||
3.7) What computer hardware should I use?
|
||||
|
||||
Operational Questions
|
||||
@ -413,8 +412,7 @@
|
||||
processes it can start by changing the max_connections value in
|
||||
postgresql.conf and restarting the postmaster.
|
||||
|
||||
3.6) Why do I need to do a dump and restore to upgrade between major
|
||||
PostgreSQL releases?
|
||||
3.6) What should I do about upgrading PostgreSQL?
|
||||
|
||||
The PostgreSQL team makes only bug fixes in minor releases, so, for
|
||||
example, upgrading from 7.4.8 to 7.4.9 does not require a dump and
|
||||
|
@ -10,7 +10,7 @@
|
||||
alink="#0000ff">
|
||||
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
|
||||
|
||||
<P>Last updated: Tue May 23 11:22:06 EDT 2006</P>
|
||||
<P>Last updated: Tue May 23 11:47:16 EDT 2006</P>
|
||||
|
||||
<P>Current maintainer: Bruce Momjian (<A href=
|
||||
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
|
||||
@ -63,8 +63,7 @@
|
||||
<A href="#item3.4">3.4</A>) What debugging features are available?<BR>
|
||||
<A href="#item3.5">3.5</A>) Why do I get <I>"Sorry, too many
|
||||
clients"</I> when trying to connect?<BR>
|
||||
<A href="#item3.6">3.6</A>) Why do I need to do a dump and restore
|
||||
to upgrade PostgreSQL releases?<BR>
|
||||
<A href="#item3.6">3.6</A> What should I do about upgrading PostgreSQL?<BR>
|
||||
<A href="#item3.7">3.7</A>) What computer hardware should I use?<BR>
|
||||
|
||||
|
||||
@ -570,8 +569,8 @@
|
||||
<I>max_connections</I> value in <I>postgresql.conf</I> and
|
||||
restarting the <I>postmaster</I>.</P>
|
||||
|
||||
<H3 id="item3.6">3.6) Why do I need to do a dump and restore
|
||||
to upgrade between major PostgreSQL releases?</H3>
|
||||
<H3 id="item3.6">3.6) What should I do about upgrading
|
||||
PostgreSQL?</H3>
|
||||
|
||||
<P>The PostgreSQL team makes only bug fixes in minor releases,
|
||||
so, for example, upgrading from 7.4.8 to 7.4.9 does not require
|
||||
|
Loading…
Reference in New Issue
Block a user