From: Jean-Michel P. <jm....@fr...> - 2003-04-28 17:53:17
|
Dear Stephane, What Php and PostgreSQL versions are you running? It may sound confusing, b= ut=20 PostgreSQL Php API was rewritten between PostgreSQL 7.2 and PostgreSQL 7.3. Therefore, it is recommended to install Php 4.3 from source and use Postgre= SQL=20 latest version. Otherwise, if you want to use RedHat stock RPMs, the=20 compatibility matrix is, as far as I noticed: =2D RedHat 7.3 and 8.0 =3D> PostgreSQL 7.2 + Php 4.2.2 (old API) =2D RedHat 9.0 =3D> PostgreSQL 7.3 + Php 4.2.2 (new API) In other words, Php seems to be broken in RedHat 7.3 and 8.0. If you are us= ing=20 the latest PostgreSQL 7.3.2 RPMs downloaded on PostgreSQL web site (like I= =20 do), you need a recent version of Php. I prepared Php 4.3.1 RPMs for my own use when I began working on PhpPgAdmin= =2E=20 Do you need them? Cheers, Jean-Michel POURE Le Lundi 28 Avril 2003 13:37, stephane parenton a =E9crit : > Hi everyone, and Jean-Michel too... > > Here's a little sum up of what happened... > > I was trying to connect as superuser (or any user in fact) through > phppgadmin in order to attack my postgres DBs. I used to have a > authentication failure. With Jean-Michel, we've seen some things, some > already done, and some not. we've seen the postgresql.conf for the > tcpip-socket to be ok, the port to be set at my will, to have > pg_hba.conf to be set the right way though the problem was still there. > > we were there when i clicked on the link pg_connect contained in the > error message... (so it reminds me to READ the error messages carefully > ;-) ). There is some comments at the bottom, and one of them said it's > better to have a user that is known as an apache user... so I've created > a superuser that has the same name as an apache user, and there we are, > the problem is solved, it works !.... i can do whatever i want with > phppgadmin... > > Thanks for helping... I'm on my way ;-) > > St=E9phane |