| From: | andrew <andrew(dot)ylzhou(at)gmail(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: filtering after join |
| Date: | 2006-01-26 12:54:23 |
| Message-ID: | 29d3b0b90601260454g35817213o7d5a0e8a1e53ddf7@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
How will the query planner do for a nesting query? Treat the
subqueries as multiple queries and then link them together?
where can I find the information (codes or documents)?
Thanks.
On 1/26/06, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> andrew wrote:
> > But the function foo() would produce different values for the two
> > queries, so the result will be different.
> > A simple example is foo() computes the sum of all the integer fields
> > of the input record.
>
> OK, I see now where you're getting at. You want to combine the record
> type of A and B into one. Then the proposed solution is right.
>
> --
> Peter Eisentraut
> http://developer.postgresql.org/~petere/
>
--
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2006-01-26 15:28:56 | Re: Changing the transaction isolation level within the stored |
| Previous Message | Markus Schaber | 2006-01-26 12:51:27 | Re: Changing the transaction isolation level within the stored |