Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Query plans for plpgsql triggers


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: "Eric B. Ridge" <ebr(at)tcdi(dot)com>
  • Cc: Postgresql <pgsql-general(at)postgresql(dot)org>
  • Subject: Re: Query plans for plpgsql triggers
  • Date: Sat, 25 Mar 2006 00:58:15 -0500
  • Message-id: <15084(dot)1143266295(at)sss(dot)pgh(dot)pa(dot)us>

"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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group