Re: SPI access to PostgreSQL query plan

From: Michael Glaesemann <grzm(at)seespotcode(dot)net>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Cc: Cristiano Duarte <cunha17(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SPI access to PostgreSQL query plan
Date: 2007-09-18 03:26:41
Message-ID: 38604477-0040-47E5-8665-CF2A07AEE0C2@seespotcode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Sep 17, 2007, at 19:46 , Florian G. Pflug wrote:

> Thats only holds true for functions in languages other than pl/sql
> (Which is
> *not* the same as pl/pgsql) - SQL functions can be inlined by the
> executor, and
> then are subject to the usual optimizations. (So they essentially
> behave like
> views).

AIUI, the stress is on the *can*, with a meaning of "may", right? Not
all SQL functions can be inlined.

Michael Glaesemann
grzm seespotcode net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-09-18 03:32:54 Re: Open issues for HOT patch
Previous Message Tom Lane 2007-09-18 03:11:32 Re: Raw device I/O for large objects