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
c120dd26
Commit
c120dd26
authored
18 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Update wording for minor release upgrades, per Alvaro.
parent
631d7018
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/installation.sgml
+5
-4
5 additions, 4 deletions
doc/src/sgml/installation.sgml
with
5 additions
and
4 deletions
doc/src/sgml/installation.sgml
+
5
−
4
View file @
c120dd26
<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.27
7
2007/01/2
7 01:27:36
momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.27
8
2007/01/2
9 21:49:17
momjian Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
...
...
@@ -385,9 +385,10 @@ su - postgres
release of <productname>PostgreSQL</>. Therefore, if you are upgrading
an existing installation that does not have a version number of
<quote>&majorversion;.x</quote>, you must back up and restore your
data. If you are upgrading from the same major version, the new version
can use your current data files so you should skip the backup and
restore steps below because they are unnecessary.
data. If you are upgrading from <productname>PostgreSQL</>
<quote>&majorversion;.x</quote>, the new version can use your current
data files so you should skip the backup and restore steps below because
they are unnecessary.
</para>
<procedure>
...
...
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