| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | eudald_v <reaven(dot)galaeindael(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Sudden connection and load average spikes with postgresql 9.3 |
| Date: | 2015-07-02 19:31:08 |
| Message-ID: | 5595917C.7090805@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2015-07-02 19:33:27 | Re: Sudden connection and load average spikes with postgresql 9.3 |
| Previous Message | Wes Vaske (wvaske) | 2015-07-02 18:00:21 | Re: New server: SSD/RAID recommendations? |