From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "Laurent Wandrebeck" <l(dot)wandrebeck(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Column level triggers |
Date: | 2008-10-15 00:47:22 |
Message-ID: | 6647.1224031642@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
> Since you can check which columns have changed, it's pretty easy to
> write a trigger that just skips its logic when none of the trigger
> columns have changed.
... which is pretty much the same thing a built-in implementation would
have to do, too. So it'd save you a bit of typing but nothing more.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-10-15 01:03:06 | Re: Drupal and PostgreSQL - performance issues? |
Previous Message | Scott Marlowe | 2008-10-15 00:31:36 | Re: how to get unique identifier for a client |
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira de Oliveira | 2008-10-15 00:52:16 | Re: autovacuum and reloptions |
Previous Message | Bruce Momjian | 2008-10-15 00:38:47 | Re: How is random_page_cost=4 ok? |