Postgres Pro
Downloads
Home   >   mailing lists

Thread: En: Error during update from version 6.5.3 to version 7.03

En: Error during update from version 6.5.3 to version 7.03

From
José Luiz
Date:
>Your install is conflicting because the package names
>are not the same. You'll need to remove the old
>package from postgres 6.5.3 (rpm -e pg_ifa)

When I did this I received the following error message:
error: removing these packages would break dependencies:
    pg_ifa is needed by mod_php-3.0.15.58
    pg_ifa is needed by pygresql-2.4.99
    pg_ifa is needed by pg_iface-6.5.3.46
    pg_ifa is needed by pgaccess-0.98.28
    libpq.so.2.0 is needed by mod_php-3.0.15.58
    libpq.so.2.0 is needed by pg_iface-6.5.3.46
    libpq.so.2.0 is needed by postgres-6.5.3.46

.> and then
> nstall the postgres 7 stuff. I just put all the RPM s

not done.

I think Suse distibution need something more.

I am sending a message to Suse asking for help too.

 José Luiz Pedroza
 jlp@macknight.com.br

Re: En: Error during update from version 6.5.3 to version 7.03

From
"ADBAAMD"
Date:
José Luiz wrote:
 >

>> Your install is conflicting because the package names
>> are not the same. You'll need to remove the old
>> package from postgres 6.5.3 (rpm -e pg_ifa)
>
> When I did this I received the following error message:
> error: removing these packages would break dependencies:
>     pg_ifa is needed by mod_php-3.0.15.58
>     pg_ifa is needed by pygresql-2.4.99
>     pg_ifa is needed by pg_iface-6.5.3.46
>     pg_ifa is needed by pgaccess-0.98.28
>     libpq.so.2.0 is needed by mod_php-3.0.15.58
>     libpq.so.2.0 is needed by pg_iface-6.5.3.46
>     libpq.so.2.0 is needed by postgres-6.5.3.46

    Perhaps you should just force install your new library instead of first
trying to remove the other ones.  If mod_php really needs the older
versions of the library, you could uprgrade it also to a newer,
compatible version; but usually there's no problem because of library
versioning: mod_php will continue to work even if you install a new
library version because the old version will be kept, just the main
symlink will point to the newer one.

    But it is always wiser to check if SuSe don't have a newer version
available, even if you have to buy the last CDs again.



--
  _
/ \   Leandro Guimarães Faria Corsetti Dutra         +55 (11) 3040 8913
\ /   Amdocs at Bell Canada                          +1 (514) 786 87 47
  X    Support Center, São Paulo, Brazil          mailto:adbaamd@bell.ca
/ \   http://terravista.pt./Enseada/1989/    mailto:leandrod@amdocs.com

pg_ctl restart?

From
Chris Smith
Date:
Hey all,

I was playing around with pg_ctl last night, and noticed that for pg_ctl
restart it doesn't seem to like the -D parameter the way I'm doing it..

What's the correct way? (This is for v7.1B4).

pgsql@elrond:~/bin$ ./pg_ctl restart -D /usr/local/pgsql/data -s -m fast
pg_ctl: cannot find /usr/local/pgsql/data/postmaster.pid
Is postmaster running?
starting postmaster anyway
pgsql@elrond:~/bin$ /usr/local/pgsql/bin/postmaster: invalid argument -- '-D'
Try '/usr/local/pgsql/bin/postmaster --help' for more information.


I do it without the -D parameter & a correct error message appears....

pgsql@elrond:~/bin$ ./pg_ctl restart -s -m fast
pg_ctl: no database directory or environment variable $PGDATA is specified
Try 'pg_ctl --help' for more information.
pgsql@elrond:~/bin$