From: | "Osborn, Jeff" <jeosborn(at)akamai(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Occasional timeouts on TRUNCATE and simple INSERTs |
Date: | 2012-12-13 20:57:21 |
Message-ID: | 4FDD5EF4-9693-443B-A721-624B0291BB20@akamai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
You all were right. The time-outs for TRUNCATE were due to a rogue pg_dump. And the issue with the inserts was due to an unrelated code change.
Thanks for your help!
--Jeff O
On Dec 11, 2012, at 5:34 PM, Osborn, Jeff wrote:
> Yeah I've been running a cron pulling relevant info from pg_stat_activity. Haven't seen anything yet. Currently looking into the pg_dump situation.
>
> --Jeff O
>
> On Dec 11, 2012, at 5:16 PM, Merlin Moncure wrote:
>
>> On Tue, Dec 11, 2012 at 3:38 PM, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> wrote:
>>
>> Yeah: absolute first thing to check is if your statements are being
>> blocked -- you can get that via pg_stat_activity from another session.
>> It's a completely different beast if that's the case.
>>
>> merlin
>
From | Date | Subject | |
---|---|---|---|
Next Message | AI Rumman | 2012-12-13 22:12:22 | Why does the number of rows are different in actual and estimated. |
Previous Message | Kevin Grittner | 2012-12-13 20:42:44 | Re: Slow queries after vacuum analyze |