| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Childs <Blue(dot)Dragon(at)blueyonder(dot)co(dot)uk>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] 7.4Beta |
| Date: | 2003-08-15 14:38:30 |
| Message-ID: | 20030815073521.B19338-100000@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Fri, 15 Aug 2003, Andreas Pflug wrote:
> Stephan Szabo wrote:
>
> >That really needs to be rewritten to do a single check over the table
> >rather than running the constraint for every row. I keep meaning to get
> >around to it and never actually do. :( I'm not sure that in practice
> >you'll get a better plan at restore time depending on what the default
> >statistics give you.
> >
> This is clearly a case for a statement level trigger, as soon as
> affected rows can be identified.
Well, I think single inserts might be more expensive (because the query is
more involved for the table joining case) using a statement level trigger,
so we'd probably want to profile the cases.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jules Alberts | 2003-08-15 14:46:08 | parameter in trigger function |
| Previous Message | Stephan Szabo | 2003-08-15 14:35:17 | Re: [GENERAL] 7.4Beta |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-08-15 14:59:09 | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
| Previous Message | Stephan Szabo | 2003-08-15 14:35:17 | Re: [GENERAL] 7.4Beta |