From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alessio Bragadini <alessio(at)albourne(dot)com> |
Cc: | PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>, Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> |
Subject: | Re: [HACKERS] Big join breaks psql |
Date: | 2000-02-22 16:20:24 |
Message-ID: | 23841.951236424@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alessio Bragadini <alessio(at)albourne(dot)com> writes:
> The following (rather long) query run fine for some time when executed
> through Micro$oft Query via Psqlodbc. We never tried it under psql.
> Today it appeared broken (some trickery on the Excel worksheet seems to
> have fix that) and for the first time I tried to run it from the command
> line. I never managed, psql always breaks in the same way:
Try doing
set ksqo = 'on';
in psql before you run the query. I think the ODBC driver does that for
you automatically.
The regular 6.5 optimizer tends to blow up when faced with large
OR-of-ANDs WHERE clauses. 7.0 will be a lot better about it...
but in the meantime you need the KSQO hack.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-02-22 16:24:10 | Re: [HACKERS] Beta for 4:30AST ... ? |
Previous Message | Tom Lane | 2000-02-22 16:12:14 | Re: [HACKERS] Re: [PATCHES] Patch for more readable parse error messages |