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
c45fa559
Commit
c45fa559
authored
18 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
In FAQ, reference upgrade info via URL.
parent
d89b9683
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/FAQ
+2
-32
2 additions, 32 deletions
doc/FAQ
doc/src/FAQ/FAQ.html
+4
-32
4 additions, 32 deletions
doc/src/FAQ/FAQ.html
with
6 additions
and
64 deletions
doc/FAQ
+
2
−
32
View file @
c45fa559
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated:
Fri Feb
2
3
1
4:06:15
E
S
T 2007
Last updated:
Tue Mar
2
0
1
3:43:40
E
D
T 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
...
...
@@ -430,37 +430,7 @@
3.6) What is the upgrade process for PostgreSQL?
PostgreSQL major releases include new features and occur roughly once
every year. A major release is numbered by increasing either the first
or second part of the version number, e.g. 8.1 to 8.2.
Major releases usually change the internal format of system tables and
data files. These changes are often complex, so we don't maintain
backward compatibility for data files. A dump/reload of the database
is required for major upgrades.
Minor releases are numbered by increasing the third part of the
version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds bug
fixes to minor releases. All users should upgrade to the most recent
minor release as soon as possible. While upgrades always have some
risk, PostgreSQL minor releases fix only frequently-encountered,
security, and data corruption bugs to reduce the risk of upgrading.
The community considers not upgrading riskier than upgrading.
`
Upgrading to a minor release does not does not require a dump and
restore; merely stop the database server, install the updated
binaries, and restart the server.
3.7) What computer hardware should I use?
Because PC hardware is mostly compatible, people tend to believe that
all PC hardware is of equal quality. It is not. ECC RAM, SCSI, and
quality motherboards are more reliable and have better performance
than less expensive hardware. PostgreSQL will run on almost any
hardware, but if reliability and performance are important it is wise
to research your hardware options thoroughly. Our email lists can be
used to discuss hardware options and tradeoffs.
See http://www.postgresql.org/support/versioning.
_________________________________________________________________
Operational Questions
...
...
This diff is collapsed.
Click to expand it.
doc/src/FAQ/FAQ.html
+
4
−
32
View file @
c45fa559
...
...
@@ -10,7 +10,7 @@
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated:
Fri Feb
2
3
1
4:06:15
E
S
T 2007
</P>
<P>
Last updated:
Tue Mar
2
0
1
3:43:40
E
D
T 2007
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:bruce@momjian.us"
>
bruce@momjian.us
</A>
)
...
...
@@ -584,37 +584,9 @@
<H3
id=
"item3.6"
>
3.6) What is the upgrade process for PostgreSQL?
</H3>
<P>
PostgreSQL major releases include new features and occur roughly
once every year. A major release is numbered by increasing either
the first or second part of the version number, e.g. 8.1 to 8.2.
<P>
Major releases usually change the internal format of system tables
and data files. These changes are often complex, so we don't maintain
backward compatibility for data files. A dump/reload of the database
is required for major upgrades.
</P>
<P>
Minor releases are numbered by increasing the third part of the
version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds
bug fixes to minor releases. All users should upgrade to the most
recent minor release as soon as possible. While upgrades always have
some risk, PostgreSQL minor releases fix only frequently-encountered,
security, and data corruption bugs to reduce the risk of upgrading.
The community considers
<i>
not
</i>
upgrading riskier than
upgrading.
</P>
`
<P>
Upgrading to a minor release does not does not require a dump and
restore; merely stop the database server, install the updated binaries,
and restart the server.
</P>
<H3
id=
"item3.7"
>
3.7) What computer hardware should I use?
</H3>
<P>
Because PC hardware is mostly compatible, people tend to believe that
all PC hardware is of equal quality. It is not. ECC RAM, SCSI, and
quality motherboards are more reliable and have better performance than
less expensive hardware. PostgreSQL will run on almost any hardware,
but if reliability and performance are important it is wise to
research your hardware options thoroughly. Our email lists can be used
to discuss hardware options and tradeoffs.
</P>
<P>
See
<a
href=
"http://www.postgresql.org/support/versioning"
>
http://www.postgresql.org/support/versioning
</a>
.
</P>
<HR>
...
...
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