Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
8c98fd6e
Commit
8c98fd6e
authored
Feb 21, 2007
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update upgrade wording.
parent
50c7e83c
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
9 deletions
+9
-9
doc/FAQ
doc/FAQ
+6
-6
doc/src/FAQ/FAQ.html
doc/src/FAQ/FAQ.html
+3
-3
No files found.
doc/FAQ
View file @
8c98fd6e
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Wed Feb 21 1
4:47:53
EST 2007
Last updated: Wed Feb 21 1
7:54:05
EST 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
...
...
@@ -431,11 +431,11 @@
3.6) What is the upgrade process for PostgreSQL?
The PostgreSQL team only adds bug fixes to minor releases. All users
should upgrade to the most recent minor release as soon as
it is
available. 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
more risky than upgrading.
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
more risky than upgrading.
Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does not
require a dump and restore; merely stop the database server, install
...
...
doc/src/FAQ/FAQ.html
View file @
8c98fd6e
...
...
@@ -10,7 +10,7 @@
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated: Wed Feb 21 1
4:47:53
EST 2007
</P>
<P>
Last updated: Wed Feb 21 1
7:54:05
EST 2007
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:bruce@momjian.us"
>
bruce@momjian.us
</A>
)
...
...
@@ -585,8 +585,8 @@
<H3
id=
"item3.6"
>
3.6) What is the upgrade process for PostgreSQL?
</H3>
<P>
The PostgreSQL team only adds bug fixes to minor releases. All
users should upgrade to the most recent minor release as soon as
it
is availa
ble. While upgrades always have some risk, PostgreSQL minor
users should upgrade to the most recent minor release as soon as
possi
ble. 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 more risky than upgrading.
</P>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment