| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Trigger on select? |
| Date: | 2005-08-03 09:23:08 |
| Message-ID: | 20050803092307.GA2991@merkur.hilbert.loc |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Tue, Aug 02, 2005 at 05:54:59PM -0700, Chris Travers wrote:
> >Hey, anyone know if it is possible to fire a trigger before a select?
> >I'm considering creating some tables which contain data summarized
> >from other tables as kind of a cache mechanism. The hope is I can
> >speed up some queries that get executed a lot (and are kind of slow)
> >by maintaining data (like sums of big columns, for example). I was
> >all ready to go and then I discovered that trigger-before-select is
> >not supported. (Is it in any DB?)
> >
> >The idea is this:
> >
> >Any time I execute a query that would access the summary data, the
> >"before select" trigger fires and goes out and builds any summary data
> >missing from the summary table.
>
> No. You must instead generate a view.
And then it needs to be a materialized view of some sort
to achieve the caching he's after.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jason.ctr.alburger | 2005-08-03 12:53:37 | SQL error code -601 <ECPG_WARNING_QUERY_IGNORED> |
| Previous Message | Kyle Bateman | 2005-08-03 01:15:27 | Trigger on select? |