Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
8188474a
Commit
8188474a
authored
22 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Update FAQ.
parent
bed81bcb
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/FAQ
+20
-1
20 additions, 1 deletion
doc/FAQ
doc/src/FAQ/FAQ.html
+1
-1
1 addition, 1 deletion
doc/src/FAQ/FAQ.html
with
21 additions
and
2 deletions
doc/FAQ
+
20
−
1
View file @
8188474a
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Tu
e
Jun
11 06:36:10
EDT 2002
Last updated: T
h
u Jun
20 22:00:57
EDT 2002
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
...
...
@@ -53,6 +53,7 @@
3.7) What debugging features are available?
3.8) Why do I get "Sorry, too many clients" when trying to connect?
3.9) What are the pg_sorttempNNN.NN files in my database directory?
3.10) Why do I need to do a dump and restore to upgrade PostgreSQL?
Operational Questions
...
...
@@ -596,6 +597,24 @@
The temporary files should be deleted automatically, but might not if
a backend crashes during a sort. If you have no backends running at
the time, it is safe to delete the pg_tempNNN.NN files.
3.10) Why do I need to do a dump and restore to upgrade PostgreSQL?
The PostgreSQL team tries very heard to maintain compatability across
minor releases. So upgrading from 7.2 to 7.2.1 does not require a dump
a restore. However, new features are continuously being adding and
sometimes this requires new fields to be added to system tables.
These changes may be across many tables and so maintaining backward
compatability would be quite difficult. Thus, restoring from a dump is
required to make everything work.
Note that the actual on-disk file format does not change very often, a
feature the pg_upgrade script uses quite successfully. There the dump
is used create the necessary information in the system tables. The
data files are then just copied across. This method is not as
guarenteed as the dump/restore method but when it works it can make
upgrades very efficient.
_________________________________________________________________
Operational Questions
...
...
This diff is collapsed.
Click to expand it.
doc/src/FAQ/FAQ.html
+
1
−
1
View file @
8188474a
...
...
@@ -14,7 +14,7 @@
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated: Tu
e
Jun
11 06:36:10
EDT 2002
</P>
<P>
Last updated: T
h
u Jun
20 22:00:57
EDT 2002
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:pgman@candle.pha.pa.us"
>
pgman@candle.pha.pa.us
</A>
)
<BR>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment