[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] [RaQ 4r] - Upgrade Postgres and upgrade php to 4.0.6
- Subject: RE: [cobalt-users] [RaQ 4r] - Upgrade Postgres and upgrade php to 4.0.6
- From: ger.oshea@xxxxxxxxxxxx
- Date: Mon Nov 5 09:55:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Hi Clark
I really appreciate you taking the time out to reply to my post.
O.K I did a search and found plpgsql.so in /usr/lib/pgsql/plpgsql.so
I modified the php.ini file and added extension=plpgsql.so ,I restarted
apache and tried to log in again to phpPgAdmin - I get this message (in a
phpinfo() format type screen)
It appears you do not have PosgreSQL functions built into PHP.
You cannot use phpPgAdmin without the pgsql extension
Check below to verify!
I did a search for pgsql.so and found it in /usr/lib/apache/php/pgsql.so
I modified the php.ini file again adding extension=pgsql.so
When I check phpinfo(); I see the pgsql extensions also I get as far as the
log in screen
But when I try to log in I get what follows.
Error
PostgreSQL said: ERROR: Attribute 'datallowconn' not found
Your query:
SELECT
d.datname as "Database",
u.usename as "Owner",
pg_encoding_to_char(d.encoding) as "Encoding",
datallowconn as "Allow Connections",
datpath as "Data Path",
obj_description(d.oid) as "Comment"
FROM
pg_database d, pg_user u
WHERE
d.datdba = u.useysid
UNION
SELECT
d.datname,
NULL AS owner,
pg_encoding_to_char(d.encoding),
datallowconn,
datpath,
obj_description(d.oid) as description
FROM
pg_database d
WHERE
d.datdba NOT IN (SELECT usesysid FROM pg_user)
ORDER BY "Database "
I haven't loaded php 4.0.6 with GD yet - I'm worried about how it might
affect what is there at the moment.
Do you know of any issues around updating to php 4.0.6 with GD?. As you
said in your post It might very well sort out my problems.
What I have done above does it seem right to you, or am I on the wrong
track?
We decided to go with postgres because we have a very complicated backend
database structure, we have unnecessary duplication between web databases
and backend databases, we hope to merge the two in the near future. We
found MySQL was not strong enough to fulfill these needs, and instead of
dedicating resources to both databases, we decided to concentrate on just
one.
Again your help is really appreciated.
Regards,
Ger O' Shea
__________________________________________
"Clark E. Morgan"
<prlhkr@xxxxxxxxxxxxx> To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent by: cc:
cobalt-users-admin@list. Subject: RE: [cobalt-users] [RaQ 4r] - Upgrade Postgres and upgrade
cobalt.com php to 4.0.6
05/11/01 12:50 PM
Please respond to
cobalt-users
> I would like to change our web database to Postgres, I know postgres is
> running because the cobalt interface uses it, but I can not connect to it
> using phpPgAdmin, I'm told it is because php is not compiled with
Postgres
> support - one thing I do not understand is php is compiled with the
> configure option '--with-apxs=/usr/sbin/apxs' I taught (correct me if I
am
> wrong) that all I would have to do is add extension=pgsql.so to php.ini
> and php would work with postgres
> I have tried this and it does not- maybe it is because I need to be at
php
> 4.0.6
The file you want to load will need to be in /usr/lib/apache and if I am
not mistaken, it's plpgsql.so. It should be somewhere on your system. If
not, you can dl the source and create one relatively easily. It has nothing
to do with your php version though it is widely said that php 4.0.x didn't
have it all together till 4.0.6 so do that anyway.
There is also the issue of having the correct username and password. I
don't
know much about how pgsql authenticates; but it's a good bet there's at
least
this much security; and you will probably want to connect from the console
first as a root user, add a special user for phppgadmin and configure
accordingly.
> I would like to do the updates above, but after they are done my MySql
and
> php will still work correctly until I have them moved over to Postgres.
> I not that worried if I can't update Postgres 7.0.2 (at the risk of
> breaking the interface - its fine) if it would only work with php and
> phpPgAdmin.
It's not my business; but you should examine your reasons for wanting to go
to Postgres. Both db's have their respective strengths; but i Know that for
my purposes, MySQL has always been a great tool, especially upgraded to
something
in the 3.23 tree where you can get transactions and a raft of more
traditional
rdbms stuff that's missing from your current version.
If you're stuck on Postgres, I'd still be inclined to skip the upgrade. It
seems to me that cobalt goes out of their way to ignore Postgres from a
user
standpoint and I'm guessing there's a reason (read support nightmare) for
mixing up user purpose with the cobalt backend. Best of luck.
Clark
_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users