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
2bd17a5f
Commit
2bd17a5f
authored
21 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Add FAQ entry on hardware selection.
parent
118ec0da
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/FAQ
+14
-2
14 additions, 2 deletions
doc/FAQ
doc/src/FAQ/FAQ.html
+13
-2
13 additions, 2 deletions
doc/src/FAQ/FAQ.html
with
27 additions
and
4 deletions
doc/FAQ
+
14
−
2
View file @
2bd17a5f
Frequently Asked Questions (FAQ) for PostgreSQL
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated:
Fri Jun 4 00:09:16
EDT 2004
Last updated:
Sun Jul 11 20:18:47
EDT 2004
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
...
@@ -54,6 +54,7 @@
...
@@ -54,6 +54,7 @@
3.9) What is in the pgsql_tmp directory?
3.9) What is in the pgsql_tmp directory?
3.10) Why do I need to do a dump and restore to upgrade PostgreSQL
3.10) Why do I need to do a dump and restore to upgrade PostgreSQL
releases?
releases?
3.10) What computer hardware should I use?
Operational Questions
Operational Questions
...
@@ -258,7 +259,7 @@
...
@@ -258,7 +259,7 @@
1.7) What is the latest release?
1.7) What is the latest release?
The latest release of PostgreSQL is version 7.4.
2
.
The latest release of PostgreSQL is version 7.4.
3
.
We plan to have major releases every six to eight months.
We plan to have major releases every six to eight months.
...
@@ -633,6 +634,17 @@
...
@@ -633,6 +634,17 @@
In releases where the on-disk format does not change, the pg_upgrade
In releases where the on-disk format does not change, the pg_upgrade
script can be used to upgrade without a dump/restore. The release
script can be used to upgrade without a dump/restore. The release
notes mention whether pg_upgrade is available for the release.
notes mention whether pg_upgrade is available for the release.
3.11) 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 you are building a server where reliability and
performance are concerns, it is wise to research your hardware options
thoroughly. Our email lists can be used to discuss hardware options
and tradeoffs.
_________________________________________________________________
_________________________________________________________________
Operational Questions
Operational Questions
...
...
This diff is collapsed.
Click to expand it.
doc/src/FAQ/FAQ.html
+
13
−
2
View file @
2bd17a5f
...
@@ -10,7 +10,7 @@
...
@@ -10,7 +10,7 @@
alink=
"#0000ff"
>
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated:
Fri Jun 4 00:09:16
EDT 2004
</P>
<P>
Last updated:
Sun Jul 11 20:18:47
EDT 2004
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:pgman@candle.pha.pa.us"
>
pgman@candle.pha.pa.us
</A>
)
<BR>
"mailto:pgman@candle.pha.pa.us"
>
pgman@candle.pha.pa.us
</A>
)
<BR>
...
@@ -76,6 +76,7 @@
...
@@ -76,6 +76,7 @@
directory?
<BR>
directory?
<BR>
<A
href=
"#3.10"
>
3.10
</A>
) Why do I need to do a dump and restore
<A
href=
"#3.10"
>
3.10
</A>
) Why do I need to do a dump and restore
to upgrade PostgreSQL releases?
<BR>
to upgrade PostgreSQL releases?
<BR>
<A
href=
"#3.11"
>
3.10
</A>
) What computer hardware should I use?
<BR>
<H2
align=
"center"
>
Operational Questions
</H2>
<H2
align=
"center"
>
Operational Questions
</H2>
...
@@ -333,7 +334,7 @@
...
@@ -333,7 +334,7 @@
<H4><A
name=
"1.7"
>
1.7
</A>
) What is the latest release?
</H4>
<H4><A
name=
"1.7"
>
1.7
</A>
) What is the latest release?
</H4>
<P>
The latest release of PostgreSQL is version 7.4.
2
.
</P>
<P>
The latest release of PostgreSQL is version 7.4.
3
.
</P>
<P>
We plan to have major releases every six to eight months.
</P>
<P>
We plan to have major releases every six to eight months.
</P>
...
@@ -806,6 +807,16 @@
...
@@ -806,6 +807,16 @@
The release notes mention whether
<I>
pg_upgrade
</I>
is available for the
The release notes mention whether
<I>
pg_upgrade
</I>
is available for the
release.
</P>
release.
</P>
<H4><A
name=
"3.11"
>
3.11
</A>
) What computer hardware should I use?
</H4>
<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 you are building a server where reliability and performance are
concerns, it is wise to research your hardware options thoroughly. Our
email lists can be used to discuss hardware options and tradeoffs.
</P>
<HR>
<HR>
<H2
align=
"center"
>
Operational Questions
</H2>
<H2
align=
"center"
>
Operational Questions
</H2>
...
...
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