Ok. I have checked.
The /etc/rc.d/init.d directory was populated with the postgresql file
after the postgresql-server-7.3.9-1PGDG.i686.rpm file was installed.
Yes, I kept track of the differences as each rpm was installed. :)
All rpm files were obtained from postgresql of course.
Let's verify the contents of the rpm file:
cp postgresql-server-7.3.9-1PGDG.i686.rpm crap
cat postgresql-server-7.3.9-1PGDG.i686.rpm | rpm2cpio | cpio -iumd
And now we have the file of concern right from the rpm file in a
directory called crap/etc/rc.d/init.d
The lines of interest in the postgresql file are still:
------------ contents of postgresql file ------
# Version 7.4 Lamar Owen.
# Version 7.4.3 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
# Support condstop for uninstall
# Minor other changes suggested by Fernando Nasser.
# Version 7.4.5 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
# Rewrite to start postmaster directly, rather than via pg_ctl; this
# fooling the postmaster's stale-lockfile check by having too many
# postgres-owned processes laying about.
# PGVERSION is:PGVERSION=7.4
So my questions still remain:
Q1: Is my fix to change PGVERSION to 7.3 from 7.4 correct in light of
the fact that the db init that occurred from the first server start
created a 7.3 database?
Q2: Did someone mistakenly put a 7.4 file in the 7.3 rpm? Does it not
matter? Outside of not being able to restart?
I do not think this is a case of installation conflicts... right? The
file has the problem right out of the rpm.
Thanks as always for the help.
In response to
pgsql-general by date
|Next:||From: Tom Lane||Date: 2005-05-02 20:06:38|
|Subject: IMPORTANT: two new PostgreSQL security problems found|
|Previous:||From: Tom Lane||Date: 2005-05-02 19:05:08|
|Subject: Re: Tuning queries inside a function |