Re: Premature view materialization in 8.2?

From: "Jonathan Ellis" <jonathan(at)utahpython(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Premature view materialization in 8.2?
Date: 2007-04-06 20:26:49
Message-ID: e06563880704061326q7872d8a8q3ab44e6971f80746@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 4/6/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > The problem seems to be that clan_members_v contains a call to an
> > expensive function:
>
> I'll bet that the function is marked VOLATILE. 8.2 is more conservative
> about optimizing away volatile functions than previous releases. If
> it has no side effects, mark it STABLE (or can it even be IMMUTABLE?).

That's exactly right, it should have been STABLE.

Thanks a lot for figuring that out for me!

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Alex Deucher 2007-04-06 20:38:33 postgres 8.2 seems to prefer Seq Scan
Previous Message Ron 2007-04-06 19:37:08 Re: SCSI vs SATA