From: Josh Berkus <josh@agliodbs.com>
To: eudald_v <reaven.galaeindael@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Sudden connection and load average spikes with postgresql 9.3
Date: Thu, 02 Jul 2015 12:31:08 -0700
Message-ID: <5595917C.7090805@agliodbs.com> (raw)
In-Reply-To: <WM!ce37b625804c9f46dcf29b027e47b98da33c7c3aa4c42b1f5931a2f12ca4e4a76682fb220cb110a9b04b41f796c700fd!@asav-3.01.com>
References: <1435675936590-5855895.post@n5.nabble.com>
<55931EB0.1000003@agliodbs.com>
<1435851680008-5856298.post@n5.nabble.com>
<WM!ce37b625804c9f46dcf29b027e47b98da33c7c3aa4c42b1f5931a2f12ca4e4a76682fb220cb110a9b04b41f796c700fd!@asav-3.01.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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
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: josh@agliodbs.com, reaven.galaeindael@gmail.com
Subject: Re: Sudden connection and load average spikes with postgresql 9.3
In-Reply-To: <5595917C.7090805@agliodbs.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