Re: Request assistance connecting with Pg::connectdb

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: public(at)ryanwright(dot)com (Ryan Wright), pgsql-general(at)postgresql(dot)org
Subject: Re: Request assistance connecting with Pg::connectdb
Date: 2002-11-27 17:31:20
Message-ID: 20021127173120.89268103C9@polaris.pinpointresearch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Just curious, have you tried:

1. using only the dbname, user and password (ie. not host or port)?

2. tried starting postmaster with the -i flag?

3. specifying localhost and port 5432 when you finre up psql?

I don't have enough knowledge of the Perl modules to speak with authority but
I have this gut-level feeling that by adding the host and port to the
connectdb command that you are causing your program to attempt to use a
network socket instead of a local unix socket to connect. You need -i to
connect via the network.

Cheers,
Steve

On Wednesday 20 November 2002 1:55 pm, Ryan Wright wrote:
> Hello,
>
> I am having a heck of a time connecting to my postgres server, and was
> hoping some kind soul would advise me on how to proceed.
>
> The problem: Perl script dies with no error message.
>
> Code snippet:
>
> $conn = Pg::connectdb("dbname=testdb host=localhost port=5432
> user=postgres password=test");
> print "status = ",$conn->status, "\n";
> die $conn->errorMessage unless PGRES_CONNECTION_OK eq $conn->status;
>
> Code output:
>
> status = 0
> Died at ./testscript.pl line 105.
>
> Other relevant information:
>
> - If I specify an incorrect database or username, I get appropriate
> error messages from postgres.
> - It doesn't matter whether I specify a correct or incorrect password;
> I get the same empty error.
> - "psql -U postgres -W testdb" works just fine. psql actually works
> perfect in every respect. I can connect, grab records, and do
> everything I should be able to do.
> - Postgres has been started correctly and netstat shows it listening
> on tcp port 5432. I accomplished this by changing tcpip_socket = true
> in postgresql.conf.
> - The machine running the script is the same machine running postgres.
> - pg_hba.conf is configured as follows:
> local all trust
> host all 127.0.0.1 255.255.255.255 trust
> host all 192.168.1.12 255.255.255.255 trust
>
> I added the server's remote IP in testing to see if it made a
> difference. It did not.
>
> Installation notes:
>
> - System is a Red Hat 7.2 box.
> - Postgres v7.2.3 was installed from RPMs yesterday. No prior version
> of Postgres has ever been installed on this server.
> - Perl version 5.6.0.
> - The Postgres Perl extensions were also installed from RPMs. They
> installed into /usr/lib/perl5/site_perl/5.6.1/i386_linux. They didn't
> work from there, so I moved the files Pg.pm, Pg.so, and autosplit.ix
> to /usr/lib/perl5/5.6.0 where my cgi-bin.pl resided.
>
> Any advice would be greatly appreciated!
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-11-27 17:41:07 Re: FATAL 1: Memory exhausted in AllocSetAlloc()
Previous Message SZUCS Gábor 2002-11-27 17:15:04 Re: Select nextval problem