Bug 251871 - init.d/postresql startup failure
init.d/postresql startup failure
Product: Fedora
Classification: Fedora
Component: postgresql (Show other bugs)
All Linux
low Severity high
: ---
: ---
Assigned To: Tom Lane
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-08-12 21:00 EDT by Tim Malnati
Modified: 2013-07-02 23:14 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-12 23:10:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Malnati 2007-08-12 21:00:38 EDT
Description of problem: Postgresql fails to startup due to version mismatch
error.  init.d script is hard coded with "PGVERSION=8.1.a" causing script to
fail version checking.

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

How reproducible: 

Steps to Reproduce:
/etc/rc.d/init.d/postgresql start (2nd and subsequent strat w/new database)
Actual results:
An old version of the database format was found.
You need to upgrade the data format before using PostgreSQL.
See (Your System's documentation directory)/postgresql-8.1.a/README.rpm-dist for
more information.
fails to start after new database is created (2nd & subsequent attempts)

Expected results: normal startup

Additional info:
Comment 1 Tom Lane 2007-08-12 22:14:15 EDT
[ blink ] ... Not here it doesn't.  To double-check, I pulled down both i386 and x86_64 versions of 
postgresql-server-8.2.4-1.fc7 from download.fedora.redhat.com, and they contain the expected
So the salient question seems to be, exactly which postgresql-server RPM did you get, from exactly where?
Comment 2 Tim Malnati 2007-08-12 22:36:56 EDT
Postgres was loaded some time ago but it unclear at the moment if it part of 
the original load or updated.  It probably came form a mirror where I use yum.  
I looked for postgresql.rpmnew and there was none though.  

If you got the correct versioning, the I suspect mine was a remnant.  Although 
I have to wonder why this would be hard coded in the script anyway.

Thanks,  Tim
Comment 3 Tom Lane 2007-08-12 23:10:39 EDT
The number is inserted into the script during RPM build, which is the same time that the binary 
executables have it hard-wired into them --- I see nothing very wrong with that.

I'm going to assume that you got a corrupt download and close this WORKSFORME.  Please reopen if you 
find some evidence that the file is actually corrupt on any Fedora distribution site.

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