| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Eric B(dot) Ridge" <ebr(at)tcdi(dot)com> |
| Cc: | Postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Query plans for plpgsql triggers |
| Date: | 2006-03-25 05:58:15 |
| Message-ID: | 15084.1143266295@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Eric B. Ridge" <ebr(at)tcdi(dot)com> writes:
> On Mar 25, 2006, at 12:24 AM, Tom Lane wrote:
>> This is the sort of detail that you really should not omit.
> I'm now curious if complex rules can influence the planner in
> negative ways.
It's possible. I'm not certain that that is really what you are
seeing, but it could be.
> ... However, I can try to work up a
> test case against 7.4.12 if you think it'll be beneficial.
I doubt we'd consider patching such a problem in 7.4. At this point
the only issues that will get patched in 7.4 are security and data-loss
risks, not performance problems.
Again: demonstrating the issue in 8.1 or CVS HEAD would be a good step
towards getting people motivated to fix it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AKHILESH GUPTA | 2006-03-25 06:36:34 | regarding join |
| Previous Message | Eric B. Ridge | 2006-03-25 05:46:49 | Re: Query plans for plpgsql triggers |