From: andrew <andrew.ylzhou@gmail.com>
To: pgsql-sql@postgresql.org
Subject: Re: filtering after join
Date: Fri, 27 Jan 2006 17:32:13 +0100
Message-ID: <29d3b0b90601270832l576b2768t493736a4cc4c88fe@mail.gmail.com> (raw)
In-Reply-To: <2048.1138373739@sss.pgh.pa.us>
References: <29d3b0b90601250927o2a5ee6e6mc33a7647da4438ce@mail.gmail.com>
<200601261222.34906.peter_e@gmx.net>
<29d3b0b90601260454g35817213o7d5a0e8a1e53ddf7@mail.gmail.com>
<200601261759.31184.peter_e@gmx.net>
<29d3b0b90601270110w645eab52k41ea6e385f297ae4@mail.gmail.com>
<29d3b0b90601270117t2a8ec180x469b2a65f6b29a13@mail.gmail.com>
<2048.1138373739@sss.pgh.pa.us>
I have traced the code. It exits when the argument is the result of a
join or a subselect in function ParseFuncOrColumn(). The reason
mentioned in the comments is lack of named tuple type. How can force
it to create such a tuple type? is there a way? thanks a million
times!
On 1/27/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> andrew <andrew.ylzhou@gmail.com> writes:
> > I got errors in this query. I have a function complete(record) which
> > takes a generic record type data. But it seems cannot be applied to a
> > sub-select result:
>
> As I seem to recall having mentioned several times already, PG 7.3 is
> really, really weak in this area. (If you ever got it to work, which
> I doubt you will, you'd probably then start to notice how badly it
> leaks memory for whole-row operations...)
>
> You should either forget this idea or invest the effort to move up
> to PG 8.1.
>
> regards, tom lane
>
--
andrew
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-sql@postgresql.org
Cc: andrew.ylzhou@gmail.com
Subject: Re: filtering after join
In-Reply-To: <29d3b0b90601270832l576b2768t493736a4cc4c88fe@mail.gmail.com>
* 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