Yes, the command-line client works fine that way.
Turns out the problem was SELinux permissions that had to be
specifically enabled.
Thanks for the suggestions and the help.
-- john
Scott Marlowe wrote:
On Mon, Mar 10, 2008 at 1:14 PM, John Cartwright
<[EMAIL PROTECTED]> wrote:
Hello A
On Mon, Mar 10, 2008 at 1:14 PM, John Cartwright
<[EMAIL PROTECTED]> wrote:
> Hello All,
>
> I'm using php 5.1.6 on a RHEL 5 system connecting to a postgresql server
> version 8.2.3. I think that TCP connections are enabled correctly in
> the server's pg_hba.conf and I can successfully connect
On Mon, 10 Mar 2008, Tom Lane wrote:
I don't know much about how to fix it, other than the extremely
brute-force tool of "setenforce 0". On current Fedora it looks like the
way is probably "setsebool -P allow_user_postgresql_connect 1", but I'm
not sure if RHEL5 uses that approach or somethin
Thanks for your reply, Tom. Not sure exactly what you mean - this is a
php script executed via apache. php scripts w/in the same directory that
don't make database connections seem to work OK.
Your suggestion is a good one though - it may be an SELinux
configuration. I'll try to pursue that
John Cartwright <[EMAIL PROTECTED]> writes:
> I'm using php 5.1.6 on a RHEL 5 system connecting to a postgresql server
> version 8.2.3. I think that TCP connections are enabled correctly in
> the server's pg_hba.conf and I can successfully connect from the client
> using pgsql. However, tryin
Hello All,
I'm using php 5.1.6 on a RHEL 5 system connecting to a postgresql server
version 8.2.3. I think that TCP connections are enabled correctly in
the server's pg_hba.conf and I can successfully connect from the client
using pgsql. However, trying to use pg_connect() w/ a call like:
