From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Walt Bigelow <walt(at)stimpy(dot)com> |
Cc: | pgsql-sql(at)hub(dot)org |
Subject: | Re: [SQL] subqueries |
Date: | 1999-04-13 23:31:11 |
Message-ID: | 463.924046271@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Walt Bigelow <walt(at)stimpy(dot)com> writes:
> On Tue, 13 Apr 1999, Tom Lane wrote:
>>>> This query returns 0 rows [ when it shouldn't ].
> The output of explain:
> NOTICE: QUERY PLAN:
> Seq Scan on tbladdress (cost=50.34 size=348 width=24)
> SubPlan
> -> Unique (cost=50.34 size=0 width=0)
> -> Sort (cost=50.34 size=0 width=0)
> -> Seq Scan on tbladdress (cost=50.34 size=348 width=4)
That looks about like what I'd expect (although I suppose you left
off the ORDER BY clause when doing the EXPLAIN? With it, there should
be a top-level Sort node).
I'm not able to duplicate your problem here on a toy table, using either
6.4.2 or 6.5-current. Perhaps there is some platform dependency
involved. Can anyone else try it?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Randal Flagg | 1999-04-14 03:02:46 | external environment variable |
Previous Message | David Sauer | 1999-04-13 16:16:53 | bug report on text text fields. WAS: Re: [SQL] Trouble with ... |