3

Folowing this question by CountZero, apparently i'm facing same problem here. When my site trying to open connection with the database, SOMETIME (Not Always) i get following error:

Warning: pg_connect() [function.pg-connect]: Unable to connect to PostgreSQL server: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. in E:\htdocs\trial_pg\client_1a.php on line 3

Here is my client1a.php script:

<?php
  $connString = 'dbname=movies user=xxxxxx password=xxxxxx';
  $connHandler = pg_connect($connString);
  echo 'Connected to '.pg_dbname($connHandler);
?>

This happens often, especially when I refresh the page (F5) repeatedly to test the connection. I'm new with postgresql, and this is the developing environment of my site:

OS: Windows 7 Professional

Web Server: Apache/2.2.14 (Win32) DAV/2 mod_ssl/2.2.14 OpenSSL/0.9.8l mod_autoindex_color mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1

PHP: 5.3.1

PostgreSQL: 8.4.3

Are there any configuration i miss? Any hints?

Thanks!

7
  • +1 for a very neatly presented question Commented Sep 9, 2010 at 15:27
  • The script name it is looking for has an '_' (underscore). client_1a.php Commented Sep 9, 2010 at 15:28
  • Could it be that php doesn't immediately close the connection on script end? I see no explicit pg_close() in your code. Look at the postgres logs for any possible details of this. Commented Sep 9, 2010 at 17:14
  • 1
    PHP should run pg_close automatically at script end. How many times are you trying to open the connection (per script run)? Once? Twice? More? Look for max_connections here postgresql.org/docs/8.4/static/runtime-config-connection.html then check your config, if you're at default of 100 that should be plenty, and sounds like it's something with the server itself. If you're opening 20+ connections on each script run (instead of reusing them) Then that could be the problem. Commented Sep 9, 2010 at 18:14
  • @AJ: Hmm, it should be client_1a.php. Thanks for the correction :) Commented Sep 12, 2010 at 13:22

2 Answers 2

4

Okay, so here is the answer of my question ;)

JUST RESTART THE POSTGRESQL SERVICE :)

I hope if everyone encountered the same problem, you know what you should do to solve it :D

Sign up to request clarification or add additional context in comments.

Comments

0

Sometimes this kind of problems are caused by over-enthusiastic antivirus software, if it monitors TCP connections. Do you have any antivirus running there?

1 Comment

I don't think so. I've been using Eset Smart Security for over 2 yrs and it's working fine even for Oracle. I think the problems is the postgresql itself ;)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.