Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZAkCa-0002xz-68 for pgsql-performance@arkaria.postgresql.org; Thu, 02 Jul 2015 19:31:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZAkCZ-0005Xs-FK for pgsql-performance@arkaria.postgresql.org; Thu, 02 Jul 2015 19:31:15 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZAkCY-0005Xg-FI for pgsql-performance@postgresql.org; Thu, 02 Jul 2015 19:31:14 +0000 Received: from 01.zmailcloud.com ([192.198.85.104] helo=mx-out-1.zmailcloud.com) by makus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1ZAkCV-0005JC-M9 for pgsql-performance@postgresql.org; Thu, 02 Jul 2015 19:31:13 +0000 Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id 4E8BE563DAD; Thu, 2 Jul 2015 14:31:11 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 3CBE9A03F5; Thu, 2 Jul 2015 14:31:11 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssxaIC9swr7c; Thu, 2 Jul 2015 14:31:11 -0500 (CDT) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 095DBA03FD; Thu, 2 Jul 2015 14:31:11 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id C8A9DA03FE; Thu, 2 Jul 2015 14:31:10 -0500 (CDT) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Py2jNFRnNwyW; Thu, 2 Jul 2015 14:31:10 -0500 (CDT) Received: from [172.47.23.103] (50-0-190-244.dsl.dynamic.fusionbroadband.com [50.0.190.244]) by smtp-out-1.01.com (Postfix) with ESMTPSA id 4E697A03F5; Thu, 2 Jul 2015 14:31:09 -0500 (CDT) Message-ID: <5595917C.7090805@agliodbs.com> Date: Thu, 02 Jul 2015 12:31:08 -0700 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: eudald_v , pgsql-performance@postgresql.org Subject: Re: Sudden connection and load average spikes with postgresql 9.3 References: <1435675936590-5855895.post@n5.nabble.com> <55931EB0.1000003@agliodbs.com> <1435851680008-5856298.post@n5.nabble.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 07/02/2015 08:41 AM, eudald_v wrote: > All that was recorded during a spike. From this log I have to point > something: > Tables TABLE_X and TABLE_Y have both a TRIGGER that does an INSERT to > TABLE_Z > As you can see, TABLE_Z was being VACUUM ANALYZED. I wonder if TRIGGERS and > VACUUM work well together, just to check another perspective. Well, it's not triggers in particular, but vacuum does create some contention and possible sluggishness. Questions: * what kind of writes to the triggers do? * can they conflict between sessions? that is, are different writes on X and/or Y possibly overwriting the same rows on Z? * is that autovacuum a regular autovacuum, or is it "to prevent wraparound"? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance