From: | andrew <andrew(dot)ylzhou(at)gmail(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: filtering after join |
Date: | 2006-01-27 16:32:13 |
Message-ID: | 29d3b0b90601270832l576b2768t493736a4cc4c88fe@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> andrew <andrew(dot)ylzhou(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Kashmira Patel (kupatel) | 2006-01-27 23:06:26 | Question about check constraints |
Previous Message | andrew | 2006-01-27 15:21:24 | Re: filtering after join |