Bug 166916 - upgrading postgresql does not warn about incompatability with older databases
Summary: upgrading postgresql does not warn about incompatability with older databases
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: release-notes
Version: devel
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Release Notes Tracker
QA Contact: David Lawrence
URL: http://fedoraproject.org/wiki/DocsPro...
Whiteboard:
Depends On:
Blocks: fc5-relnotes-traqr
TreeView+ depends on / blocked
 
Reported: 2005-08-27 16:04 UTC by Nicola Soranzo
Modified: 2007-04-18 17:30 UTC (History)
2 users (show)

Fixed In Version: WIKI
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-24 16:32:55 UTC
Embargoed:


Attachments (Terms of Use)

Description Nicola Soranzo 2005-08-27 16:04:28 UTC
Description of problem, bug, incorrect information, or enhancement request:

When upgrading Fedora, if PostgreSQL is upgraded to a new major release (as with
FC3 to FC4), the user should be warned that old databases wouldn't be accessible
anymore. For PostgreSQL 7.x -> 8.0 upgrade procedure see:

http://www.postgresql.org/docs/8.0/interactive/install-upgrading.html


Version of release notes this bug refers to:

Fedora Core 4 final release

Comment 1 Rahul Sundaram 2005-08-27 16:17:47 UTC
Thank you for the report. Does Postgres break the database format in every major
release?. At any case this is something the installer should potentially warn
about if not taking care of the migration process required itself or through the
postgres package.If this is not feasible we can look into documenting a warning
in the release notes.  

Reassigning it to component Anaconda and corresponding maintainer

Comment 2 Nicola Soranzo 2005-08-27 16:28:35 UTC
(In reply to comment #1)
> Thank you for the report. Does Postgres break the database format in every 
> major release?.

Presently yes, at every first or second number change (eg. 7.2.x -> 7.3.y or
7.4.x -> 8.0.y).


Comment 3 Jeremy Katz 2005-08-29 18:41:15 UTC
It's impossible for the installer to know and be able to warn about every
incompatibility in every package.

In general, packages should handle this sanely for themselves.  Traditionally,
postgresql has only been handled by a release notes entry :/

Comment 4 Tom Lane 2005-08-29 18:54:44 UTC
Yeah, this is a problem the upstream project has struggled with and not really
found any satisfactory answer to.  We tried auto-upgrade support in the RPMs for
awhile, but that didn't work decently either, so we eventually gave it up. 
Basically this is something that has to be mentioned in the release notes every
time we update to a new major Postgres release.

(Hmm, do we have a "release notes" component I could reassign this to?  I'm not
seeing one in the menu ...)

Comment 5 Karsten Wade 2005-08-29 19:04:10 UTC
Yeah, we do, different product.  You have to reassign and do an extra step,
which is what I'm about to do when I commit this change:

1. Pick product, Fedora Documentation
2. Commit change
3. Next page lets you pick new component within the new product
4. Choose release-notes component and commit

All is good from there, should be reassigned now.

You can also always add relnotes in the Cc: if you want us to
note a bug without having to reassign it.

Comment 6 Karsten Wade 2005-08-29 19:05:22 UTC
Maybe I missed something, this should fix it.

Comment 7 Robert 'Bob' Jensen 2006-02-24 08:01:27 UTC
This bug has been fixed for the FC5 release notes
http://fedoraproject.org/wiki/Docs/Beats/DatabaseServers

Comment 8 Karsten Wade 2006-02-24 16:32:55 UTC
This same topic was addressed (and now resolved) in bug #182705.

This is fixed in the Wiki and shall be the source for the FC5 final release notes.


Note You need to log in before you can comment on or make changes to this bug.