There is also a Postgres conf file somewhere (I'll find it tomorrow, and mail it's location. I think in the same directory as pg_hba.) Anyways, either the first or second line of the file will be something like
Network Access = False You'll need to change that to true, or it won't listen for a tcp/ip connection (pgADMIN). I set it up a while ago, and haven't needed back in there, so I can't remember exactly where it all was located. Sorry. Hopefully this'll help point you in the right direction. Kev. ----- Original Message ----- From: "Aaron J. Seigo" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 19, 2003 9:53 PM Subject: Re: (clug-talk) Postgres Gurus? > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wednesday 19 February 2003 09:03, Johnny Stork wrote: > > Here's what I got now Aaron... > > i really didn't understand what you wrote. sorry =/ > > but auth with pgsql is really quite straightforward. here's two pages that lay > it out quite clearly: > > http://candle.pha.pa.us/main/writings/pgsql/sgml/client-authentication.html > http://candle.pha.pa.us/main/writings/pgsql/sgml/auth-methods.html > > maybe once you're rested up again given them a read and another go at it. > > - -- > Aaron J. Seigo > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > KDE: The 'K' is for 'kick ass' > http://www.kde.org http://promo.kde.org/3.1/feature_guide.php > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > > iD8DBQE+VF871rcusafx20MRApawAJ9pc3Tq/xXzCyMqcXy25HR5q70YYwCcCgHr > ae6sjOBmS9hlL+ZBiJhB/a4= > =LcQj > -----END PGP SIGNATURE----- > > >
