From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
---|---|
To: | Rural Hunter <ruralhunter(at)gmail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: How to investiage slow insert problem |
Date: | 2013-08-20 03:01:10 |
Message-ID: | CAL_0b1so15Q=J149nH4FmU2_CYx=wURMknYbdWTOWmqZ4pygpQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Aug 19, 2013 at 7:45 PM, Rural Hunter <ruralhunter(at)gmail(dot)com> 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.
>
> 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.
Next time, when you face this again, set log_min_duration_statement to
the value less that the age of hunging inserts and debug_print_parse,
debug_print_rewritten, debug_print_plan and debug_pretty_print to
'on'. It will allow you to log what is happening with these inserts
and what takes so many time.
--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA
http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2013-08-20 04:34:07 | Re: How to investiage slow insert problem |
Previous Message | Rural Hunter | 2013-08-20 02:45:18 | Re: How to investiage slow insert problem |