From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gavin M. Roy <gmr@myyearbook.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: SQL Function Slowness, 8.3.0
Date: Wed, 16 Apr 2008 11:09:47 -0400
Message-ID: <8328.1208358587@sss.pgh.pa.us> (raw)
In-Reply-To: <af1bce590804160806t58f7da1g50fc697dd9e6ab08@mail.gmail.com>
References: <af1bce590804160806t58f7da1g50fc697dd9e6ab08@mail.gmail.com>
"Gavin M. Roy" <gmr@myyearbook.com> writes:
> In 8.3.0, I'm seeing some oddities with SQL functions which I thought were
> immune to the planner data restrictions of plpgsql functions and the sort.
Without a specific example this discussion is pretty content-free, but
in general SQL functions face the same hazards of bad parameterized
plans as plpgsql functions do.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, gmr@myyearbook.com
Subject: Re: SQL Function Slowness, 8.3.0
In-Reply-To: <8328.1208358587@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox