于 2013/8/20 12:34, Jeff Janes 写道:
On Monday, August 19, 2013, Rural Hunter wrote:
I think that this should generally not happen at the server
if you are using pgbouncer, as you should configure it so that
pgbouncer has a lower limit than postg
On Monday, August 19, 2013, Rural Hunter wrote:
> Hi,
>
> I'm on 9.2.4 with Ubuntu server. There are usually hundereds of
> connections doing the same insert with different data from different
> networks every minute, through pgbouncer in the same network of the
> database server. The database has
On Mon, Aug 19, 2013 at 7:45 PM, Rural Hunter wrote:
>> You mentioned the "incomplete message from client" error, so it might
>> somehow be a network problem that led to a hunging connection to pgbouncer,
>> that made pgbouncer kept a connection to postgres after transaction was
>> started.
>
> pg
于 2013/8/20 10:38, Sergey Konoplev 写道:
On Mon, Aug 19, 2013 at 6:44 PM, Rural Hunter wrote:
What do you mean by recycling pgbouncer?
I mean restarting pgbouncer.
Haven't you noticed what was in the state column of the
pg_state_activity view? In 9.2 the query column in this view shows the
las
On Mon, Aug 19, 2013 at 6:44 PM, Rural Hunter wrote:
> I'm on 9.2.4 with Ubuntu server. There are usually hundereds of connections
> doing the same insert with different data from different networks every
> minute, through pgbouncer in the same network of the database server. The
> database has be
Hi,
I'm on 9.2.4 with Ubuntu server. There are usually hundereds of
connections doing the same insert with different data from different
networks every minute, through pgbouncer in the same network of the
database server. The database has been running for about one year
without problem. Yeste
