Re: psql or pgbouncer bug?

> What's in the postmaster log?

Excerpts from both postmater and pgbouncer logs see below. I can't find
nothing more interesting, no errors.

There is difference between server clocks, pgbouncer is 40s behind
postgresql server, will fix...

Kuba

Postmaster:

2010-05-21 15:58:58 CEST 20436 1 [unknown]@ [unknown] LOG:  connection
received: host=x.x.x.x port=59694

2010-05-21 15:58:58 CEST 20436 2 user@x.x.x.x(59694) database LOG:
connection authorized: user=user database=database

2010-05-21 16:00:43 CEST 20436 3 user@x.x.x.x(59694) database LOG:
unexpected EOF on client connection

2010-05-21 16:00:44 CEST 20436 4 user@x.x.x.x(59694) database LOG:
disconnection: session time: 0:01:46.642 user=user database=database
host=x.x.x.x port=59694

2010-05-21 16:00:56 CEST 20643 1 [unknown]@ [unknown] LOG:  connection
received: host=x.x.x.x port=59901

2010-05-21 16:00:56 CEST 20643 2 user@x.x.x.x(59901) database LOG:
connection authorized: user=user database=database

2010-05-21 16:01:07 CEST 20643 3 user@x.x.x.x(59901) database WARNING:
there is no transaction in progress

Pgbouncer:

2010-05-21 15:58:16.905 30404 LOG C-0x2ab248086300:
database/user@x.x.x.x:35275 login successful: db=database user=user

2010-05-21 15:58:18.698 30404 LOG S-0x2ab2481306e0:
database/user@x.x.x.x:5432 new connection to server

[restart]
2010-05-21 16:00:04.430 30404 LOG Got SIGTERM, fast exit
2010-05-21 16:00:08.104 32225 LOG File descriptor limit: 65535
(H:65535), max_client_conn: 6000, max fds possible: 60642010
2010-05-21 16:00:08.105 32227 LOG listening on *:5432
2010-05-21 16:00:08.105 32227 LOG listening on unix:/tmp/.s.PGSQL.5432

2010-05-21 16:00:17.286 32227 LOG C-0xa65bbf8:
database/user@x.x.x.x:51814 login successful: db=database user=user

2010-05-21 16:00:17.286 32227 LOG S-0xa6799e0:
database/user@x.x.x.x:5432 new connection to server

Dne 21.5.2010 17:28, Tom Lane napsal(a):
> Jakub Ouhrabka<kuba@comgate.cz>  writes:
>> can anyone tell me how this could happen, please?
>
>> database=# begin; update table set col = 100;
>> 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: Succeeded.
>> UPDATE 153
>> database=# ROLLBACK ;
>> WARNING:  there is no transaction in progress
>> ROLLBACK
>
> What's in the postmaster log?
>
>             regards, tom lane