Hi Tom,
I can assure you that there are no problem anymore now that I have put the
password.
However the modification pg_hba.conf has been done a few days ago and
never noticed the error until today where I had a *LOT* of visits to my
site.
So I still think it's a matter of bad connection delay.
Connexion where comming very fast and postmaster did'nt release them fast
enough.
I now have this problem when I run vacuum analyze:
Script started on Mon Oct 21 18:20:35 2002
~ 18:20:35: psql pyrenet
Password:
Welcome to psql, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit
pyrenet=# VACUUM ANALYZE ;
FATAL 2: could not open transaction-commit log directory
(/usr/local/pgsql/data/pg_clog): Too many open files
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: NOTICE: Message from
PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
Failed.
!# \q
~ 18:21:21: psql pyrenet
Password:
Welcome to psql, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit
pyrenet=# VACUUM ANALYZE ;
FATAL 2: could not open transaction-commit log directory
(/usr/local/pgsql/data/pg_clog): Too many open files
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!# \q
script done on Mon Oct 21 18:21:51 2002
What causes (FILES=64).
Again, this is the very first time I have such problems on postgresql!!
It works so well, it's the central point of my system!!
On Mon, 21 Oct 2002, Tom Lane wrote:
> Date: Mon, 21 Oct 2002 11:35:33 -0400
> From: Tom Lane <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: pgsql-hackers list <[EMAIL PROTECTED]>
> Subject: Re: [HACKERS] Please help
>
> Olivier PRENANT <[EMAIL PROTECTED]> writes:
> > It seems that connection from php pg_connect not supplying a password
> > lives the process for a "certain ammount of time" running, then postmaster
> > just hangs.
>
> That's hard to believe. In 7.2 or later, the backend should give up and
> close the connection and exit if the client doesn't finish the
> authentication handshake within 60 seconds.
>
> Can anyone else reproduce a problem with lack of a password on a PHP
> connection?
>
> regards, tom lane
>
--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: [EMAIL PROTECTED]
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
