Skip site navigation (1) Skip section navigation (2)

Re: Minimizing dead tuples caused by update triggers

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: Decibel! <decibel(at)decibel(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dan Harris <fbsd(at)drivefaster(dot)net>
Subject: Re: Minimizing dead tuples caused by update triggers
Date: 2007-12-20 11:14:34
Message-ID: 200712201214.37113.dfontaine@hi-media.com (view raw or flat)
Thread:
Lists: 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

In response to

pgsql-performance by date

Next:From: Alvaro HerreraDate: 2007-12-20 13:35:59
Subject: Re: Reinitialising stats once only without restarting
Previous:From: Anton MelserDate: 2007-12-20 10:05:20
Subject: Reinitialising stats once only without restarting

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group