| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: More FK patches |
| Date: | 2001-11-13 04:07:04 |
| Message-ID: | 625.1005624424@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> This patch should help fix cases with two separate fk constraints
> in a row that happen to reference the same pk constraint with
> an on update cascade and similar cases.
Aren't those NOT EXISTS clauses going to cause a humungous
performance hit?
Seems it would be better for the RI triggers to do more in C code
and stop expecting the query engine to handle these things. I've
always thought that ReferentialIntegritySnapshotOverride was an
absolutely unacceptable kluge, not least because it's turned on
*before* we do parsing/planning of the RI queries, and so is
likely to screw up system catalog checks.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2001-11-13 08:25:11 | Re: [PATCHES] More FK patches |
| Previous Message | Stephan Szabo | 2001-11-13 02:50:17 | Foreign key referential actions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2001-11-13 08:18:33 | Re: stupid patch of pg_dumplo |
| Previous Message | Stephan Szabo | 2001-11-13 02:22:15 | More FK patches |