Thread: Upgrade
A new system came in with RH7.1 and PG7.0.3 installed (no data). I want to upgrade to PG7.1.3 After reading README.rpm-dist, it is my understanding that rpm -U postgresql713 followed by the db initialization is enough. The system locale is en_US; I will change it to C. The question is: when the new database is initialized, will it take the system locale (hopefully C by that time :-), or will it import it from the old installation (en_US)? Thank you all.
On Friday 19 October 2001 02:56 pm, Mihai Gheorghiu wrote: > A new system came in with RH7.1 and PG7.0.3 installed (no data). > I want to upgrade to PG7.1.3 After reading README.rpm-dist, it is my > understanding that rpm -U postgresql713 followed by the db initialization > is enough. If /etc/rc.d/init.d/postgresql has never been run, you are correct. Simply chkconfig --level xyz postgresql on (where xyz is the set of levels in which postmaster should) will make it automatically start on the next boot. If you just want it in the current level, you may omit the --level and the xyz. The first time /etc/rc.d/init.d/postgresql start is run, an initdb will be performed for you automagically. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
Thank you very much.
I copied all rpms in /root/pg and proceeded as root.
[root@localhost pg]# rpm -U --force postgresql*
error: failed dependencies:
mx is needed by postgresql-python-7.1.3-1PGDG
I don't need python, so I remove it:
[root@localhost pg]# rm postgresql-python-7.1.3-1PGDG.i386.rpm
rm: remove `postgresql-python-7.1.3-1PGDG.i386.rpm'? y
[root@localhost pg]# rpm -U --force postgresql*
error: failed dependencies:
postgresql = 7.0.3 is needed by postgresql-python-7.0.3-8
Same without --force.
What would you suggest :-) Thanks in advance.
-----Original Message-----
From: Lamar Owen <lamar.owen@wgcr.org>
To: Mihai Gheorghiu <tanethq@earthlink.net>; pgsql-general@postgresql.org
<pgsql-general@postgresql.org>
Date: Friday, October 19, 2001 7:34 PM
Subject: Re: [GENERAL] Upgrade
>On Friday 19 October 2001 02:56 pm, Mihai Gheorghiu wrote:
>> A new system came in with RH7.1 and PG7.0.3 installed (no data).
>> I want to upgrade to PG7.1.3 After reading README.rpm-dist, it is my
>> understanding that rpm -U postgresql713 followed by the db initialization
>> is enough.
>
>If /etc/rc.d/init.d/postgresql has never been run, you are correct.
>
>Simply chkconfig --level xyz postgresql on (where xyz is the set of levels
in
>which postmaster should) will make it automatically start on the next boot.
>If you just want it in the current level, you may omit the --level and the
>xyz.
>
>The first time /etc/rc.d/init.d/postgresql start is run, an initdb will be
>performed for you automagically.
>--
>Lamar Owen
>WGCR Internet Radio
>1 Peter 4:11
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
"Mihai Gheorghiu" <tanethq@earthlink.net> writes: > [root@localhost pg]# rpm -U --force postgresql* > error: failed dependencies: > postgresql = 7.0.3 is needed by postgresql-python-7.0.3-8 > > Same without --force. > > What would you suggest :-) Thanks in advance. Best thing to do is explicitly remove the existing RPMS: # rpm -q -a | grep '^postgresql' | xargs rpm -e Then do 'rpm -U' (without --force, you shouldn't need it). What is happening is that '-U' isn't removing 'postgresql-python' (since you're not upgrading it) but it depends on the main postgresql RPM which is being upgraded. You could also just remove the 'postgresql-python' package and then do '-U'. -Doug -- Let us cross over the river, and rest under the shade of the trees. --T. J. Jackson, 1863
--force doesn't work with upgrades. use --nodeps. Keary Suska Esoteritech, Inc. "Leveraging Open Source for a better Internet" > From: "Mihai Gheorghiu" <tanethq@earthlink.net> > Date: Mon, 22 Oct 2001 10:54:19 -0400 > To: <pgsql-general@postgresql.org> > Subject: Re: [GENERAL] Upgrade > > Thank you very much. > I copied all rpms in /root/pg and proceeded as root. > > [root@localhost pg]# rpm -U --force postgresql* > error: failed dependencies: > mx is needed by postgresql-python-7.1.3-1PGDG > > I don't need python, so I remove it: > > [root@localhost pg]# rm postgresql-python-7.1.3-1PGDG.i386.rpm > rm: remove `postgresql-python-7.1.3-1PGDG.i386.rpm'? y > [root@localhost pg]# rpm -U --force postgresql* > error: failed dependencies: > postgresql = 7.0.3 is needed by postgresql-python-7.0.3-8 > > Same without --force. > > What would you suggest :-) Thanks in advance. > > > -----Original Message----- > From: Lamar Owen <lamar.owen@wgcr.org> > To: Mihai Gheorghiu <tanethq@earthlink.net>; pgsql-general@postgresql.org > <pgsql-general@postgresql.org> > Date: Friday, October 19, 2001 7:34 PM > Subject: Re: [GENERAL] Upgrade > > >> On Friday 19 October 2001 02:56 pm, Mihai Gheorghiu wrote: >>> A new system came in with RH7.1 and PG7.0.3 installed (no data). >>> I want to upgrade to PG7.1.3 After reading README.rpm-dist, it is my >>> understanding that rpm -U postgresql713 followed by the db initialization >>> is enough. >> >> If /etc/rc.d/init.d/postgresql has never been run, you are correct. >> >> Simply chkconfig --level xyz postgresql on (where xyz is the set of levels > in >> which postmaster should) will make it automatically start on the next boot. >> If you just want it in the current level, you may omit the --level and the >> xyz. >> >> The first time /etc/rc.d/init.d/postgresql start is run, an initdb will be >> performed for you automagically. >> -- >> Lamar Owen >> WGCR Internet Radio >> 1 Peter 4:11 >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 4: Don't 'kill -9' the postmaster > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org >
On Mon, 22 Oct 2001, Mihai Gheorghiu wrote:
> [root@localhost pg]# rpm -U --force postgresql*
> error: failed dependencies:
> postgresql = 7.0.3 is needed by postgresql-python-7.0.3-8
>
> Same without --force.
>
> What would you suggest :-) Thanks in advance.
Two things:
1) Don't use the '--force' option except as a last resort. 99.44% of the
time you don't need it. I've used '--nodeps' when the dependency is there
but not visible to the package database.
2) As root, type 'rpm -e postgresql-python-7.0.8-8' and get rid of the
offender.
Then do 'rpm -Uvh postgresql-*'. The 'v' is for verbose (gives you
messages about progress or the lack thereof) and the 'h' is for hashmarks
that illustrate progress.
Good luck!
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
http://www.appl-ecosys.com
Thank you all. It's working OK now. -----Original Message----- From: Rich Shepard <rshepard@appl-ecosys.com> To: Mihai Gheorghiu <tanethq@earthlink.net> Cc: pgsql-general@postgresql.org <pgsql-general@postgresql.org> Date: Monday, October 22, 2001 6:14 PM Subject: Re: [GENERAL] Upgrade >On Mon, 22 Oct 2001, Mihai Gheorghiu wrote: > >> [root@localhost pg]# rpm -U --force postgresql* >> error: failed dependencies: >> postgresql = 7.0.3 is needed by postgresql-python-7.0.3-8 >> >> Same without --force. >> >> What would you suggest :-) Thanks in advance. > > Two things: > > 1) Don't use the '--force' option except as a last resort. 99.44% of the >time you don't need it. I've used '--nodeps' when the dependency is there >but not visible to the package database. > > 2) As root, type 'rpm -e postgresql-python-7.0.8-8' and get rid of the >offender. > > Then do 'rpm -Uvh postgresql-*'. The 'v' is for verbose (gives you >messages about progress or the lack thereof) and the 'h' is for hashmarks >that illustrate progress. > >Good luck! > >Rich > >Dr. Richard B. Shepard, President > > Applied Ecosystem Services, Inc. (TM) > 2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A. > + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com > http://www.appl-ecosys.com >