But he's testing with v8 beta3, so you'd expect the typecast problem not to appear?
Are all tables fully vacuumed? Should the statistics-target be raised for some columns, perhaps? What about the config
file?
--Tim
-----Original Message-----
From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org]On Behalf Of Matt Clark
Sent: Friday, October 15, 2004 12:37 PM
To: 'Bernd'; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Select with qualified join condition / Batch inserts
> SELECT cmp.WELL_INDEX, cmp.COMPOUND, con.CONCENTRATION
> FROM SCR_WELL_COMPOUND cmp, SCR_WELL_CONCENTRATION con
> WHERE cmp.BARCODE=con.BARCODE
> AND cmp.WELL_INDEX=con.WELL_INDEX
> AND cmp.MAT_ID=con.MAT_ID
> AND cmp.MAT_ID = 3
> AND cmp.BARCODE='910125864'
> AND cmp.ID_LEVEL = 1;
Quick guess - type mismatch forcing sequential scan. Try some quotes:
AND cmp.MAT_ID = '3'
AND cmp.BARCODE='910125864'
AND cmp.ID_LEVEL = '1';
M
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
