From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
---|---|
To: | Felix Morley Finch <felix(at)crowfix(dot)com> |
Cc: | hackers(at)postgresql(dot)org |
Subject: | Re: [QUESTIONS] Join-crazy newbie may be pushing the limits :-) |
Date: | 1998-01-19 04:06:09 |
Message-ID: | 34C2D131.24E714D9@sable.krasnoyarsk.su |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Felix Morley Finch wrote:
>
> >>In article <34C1BD06(dot)1712ABAC(at)sable(dot)krasnoyarsk(dot)su>, "Vadim B. Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> writes:
>
> > Felix Morley Finch wrote:
> >>
> >> I tried searching and ran into several new lessons in SQL; I ended up
> >> with this --
> >>
> >> select name from names n, keys k1, keys k2, family f1, family f2
> >> where ((k1.key ~* 'xyzzy') and (k1.id = f1.key) and (n.id = f1.name))
> >> or ((k2.key ~* 'plugh) and (k2.id = f2.key) and (n.id = f2.name));
> >>
> >> and psql never returned. This is a test database, maybe 20 records.
> >> If I keep it down to a single keyword, it works fine.
>
> > EXPLAIN ?
> > Did you try SET geqo TO 'on=1' ?
>
> I just tried it --
>
> WARN:Bad value for # of relations (1)
>
> I tried ON=2 which gave no WARNING but didn't fix the join. I tried
> OFF and same result.
(So, this is problem of not just old optimizer...)
Could you post me output of
EXPLAIN VERBOSE _select_statement_ ?
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-01-19 05:54:49 | subselects |
Previous Message | Martin J. Laubach | 1998-01-19 03:18:34 | Re: [HACKERS] Re: New pg_pwd patch and stuff |