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 15:21:24 |
Message-ID: | 29d3b0b90601270721g1cc4a40dib9b8ff00d953e293@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Sorry. I am working on a research prototype built on 7.3 which contains
a cosiderable amount of efforts. The original developers of the prototype
have no interest in upgrading it. It is also impossible for me to upgrade it
by myself. Could you give me any tips to sovle the current problem? Thanks!
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 | andrew | 2006-01-27 16:32:13 | Re: filtering after join |
Previous Message | Tom Lane | 2006-01-27 14:55:39 | Re: filtering after join |