From: Rural Hunter <ruralhunter@gmail.com>
To: Sergey Konoplev <gray.ru@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: How to investiage slow insert problem
Date: Tue, 20 Aug 2013 10:45:18 +0800
Message-ID: <5212D83E.4080709@gmail.com> (raw)
In-Reply-To: <CAL_0b1vY=3e8c3WCrOWWh6Jk=HgVjKjk41Mv8EQpMyzUdW_3yg@mail.gmail.com>
References: <5212CA07.6020509@gmail.com>
<CAL_0b1vY=3e8c3WCrOWWh6Jk=HgVjKjk41Mv8EQpMyzUdW_3yg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
δΊ 2013/8/20 10:38, Sergey Konoplev ει:
> On Mon, Aug 19, 2013 at 6:44 PM, Rural Hunter <ruralhunter@gmail.com> 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
> last statement that was executed in this connection, and it does not
> mean that this statement is working at the moment of monitoring. If
> the state is active, than it was working, however, my assumption is
> that it was IDLE in transaction.
No, they are alll with 'active' state.
> 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.
pgbouncer and the db server are in the same local network and there
shouldn't be any network problem between them. I also ran ping from
pgbouncer server to the db server and there was no problem.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ruralhunter@gmail.com, gray.ru@gmail.com
Subject: Re: How to investiage slow insert problem
In-Reply-To: <5212D83E.4080709@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox