Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit8188474

Browse files
committed
Update FAQ.
1 parentbed81bc commit8188474

File tree

2 files changed

+21
-2
lines changed

2 files changed

+21
-2
lines changed

‎doc/FAQ

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated:Tue Jun11 06:36:10 EDT 2002
4+
Last updated:Thu Jun20 22:00:57 EDT 2002
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -53,6 +53,7 @@
5353
3.7) What debugging features are available?
5454
3.8) Why do I get "Sorry, too many clients" when trying to connect?
5555
3.9) What are the pg_sorttempNNN.NN files in my database directory?
56+
3.10) Why do I need to do a dump and restore to upgrade PostgreSQL?
5657

5758
Operational Questions
5859

@@ -596,6 +597,24 @@
596597
The temporary files should be deleted automatically, but might not if
597598
a backend crashes during a sort. If you have no backends running at
598599
the time, it is safe to delete the pg_tempNNN.NN files.
600+
601+
3.10) Why do I need to do a dump and restore to upgrade PostgreSQL?
602+
603+
The PostgreSQL team tries very heard to maintain compatability across
604+
minor releases. So upgrading from 7.2 to 7.2.1 does not require a dump
605+
a restore. However, new features are continuously being adding and
606+
sometimes this requires new fields to be added to system tables.
607+
608+
These changes may be across many tables and so maintaining backward
609+
compatability would be quite difficult. Thus, restoring from a dump is
610+
required to make everything work.
611+
612+
Note that the actual on-disk file format does not change very often, a
613+
feature the pg_upgrade script uses quite successfully. There the dump
614+
is used create the necessary information in the system tables. The
615+
data files are then just copied across. This method is not as
616+
guarenteed as the dump/restore method but when it works it can make
617+
upgrades very efficient.
599618
_________________________________________________________________
600619

601620
Operational Questions

‎doc/src/FAQ/FAQ.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
alink="#0000ff">
1515
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
1616

17-
<P>Last updated:Tue Jun11 06:36:10 EDT 2002</P>
17+
<P>Last updated:Thu Jun20 22:00:57 EDT 2002</P>
1818

1919
<P>Current maintainer: Bruce Momjian (<Ahref=
2020
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp