Re: 7.3.9 Install Question - init.d/postgresql error?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsqlrpms-hackers(at)pgfoundry(dot)org
Cc: Dianne Chen <diana_chen23(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: 7.3.9 Install Question - init.d/postgresql error?
Date: 2005-05-02 20:25:02
Message-ID: 2587.1115065502@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dianne Chen <diana_chen23(at)yahoo(dot)com> writes:
> Let's verify the contents of the rpm file:

> mkdir crap
> cp postgresql-server-7.3.9-1PGDG.i686.rpm crap
> cd 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
> avoids
> # fooling the postmaster's stale-lockfile check by having too many
> # postgres-owned processes laying about.

> # PGVERSION is:PGVERSION=7.4
> -----------------------------------------------

Hmm. Apparently Devrim stuck the 7.4 initscript into the 7.3.9 RPMs.
Not good :-(

> 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?

It will probably work, but I haven't compared the 7.3 and 7.4
initscripts in detail.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Wheeler 2005-05-02 20:38:44 Re: [Dbdpg-general] Re: 'prepare' is not quite schema-safe
Previous Message Tom Lane 2005-05-02 20:06:38 IMPORTANT: two new PostgreSQL security problems found