Bug 160463 - postgresql installed by FC4 needs a different data format than FC3
postgresql installed by FC4 needs a different data format than FC3
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: postgresql (Show other bugs)
4
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Tom Lane
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-15 06:11 EDT by Flavio Cardone
Modified: 2013-07-02 23:06 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-15 10:03:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Flavio Cardone 2005-06-15 06:11:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
FC3 had postgresql 7.4 but FC4 has 8.0.3. The latter will not start and reports that the data format needs to be updated. However, to update the data according to the instructions by postgresql.org you need to have a running postgresql server. Catch 22.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. have postgresql in FC3
2. install FC4
3. try starting postgresql
  

Additional info:
Comment 1 Tom Lane 2005-06-15 10:03:26 EDT
You have to dump and restore the old database.  This has always been true of
every major Postgres version upgrade, and 7.4 -> 8.0 is no different.
Comment 2 Flavio Cardone 2005-06-16 04:48:34 EDT
Yes, of course, but if you install FC4 (postgres 8.0) over FC3 (postgres 7.4),
you only realize you had to dump your database after you already installed FC4.
And once you installed FC4, you can't dump your database because postgres 8.0
won't start...

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