Re: Minimizing dead tuples caused by update triggers - Mailing list pgsql-performance

From Dimitri Fontaine
Subject Re: Minimizing dead tuples caused by update triggers
Date
Msg-id 200712201214.37113.dfontaine@hi-media.com
Whole thread Raw
In response to Re: Minimizing dead tuples caused by update triggers  (Decibel! <decibel@decibel.org>)
List pgsql-performance
Le jeudi 20 décembre 2007, Decibel! a écrit :
> A work-around others have used is to have the trigger just insert
> into a 'staging' table and then periodically take the records from
> that table and summarize them somewhere else.

And you can even use the PgQ skytools implementation to easily have this kind
of 'staging'-table with a producer and one or many subscribers. See those
references if you're interrested:
http://kaiv.wordpress.com/2007/10/19/skytools-database-scripting-framework-pgq/
  http://skytools.projects.postgresql.org/doc/pgq-sql.html
  http://skytools.projects.postgresql.org/doc/pgq-admin.html
  http://skytools.projects.postgresql.org/doc/pgq-nodupes.html

Hope this helps, regards,
--
dim

Attachment

pgsql-performance by date:

Previous
From: "Anton Melser"
Date:
Subject: Reinitialising stats once only without restarting
Next
From: Alvaro Herrera
Date:
Subject: Re: Reinitialising stats once only without restarting