>> > Query: >> > >> > select A0.Subj, A2.Obj From jena_g1t1_stmt A0, jena_g1t1_stmt A1, >> > jena_g1t1_stmt A2 Where >> > A0.Prop='Uv::http://prismstandard.org/namespaces/1.2/basic/isPartOf' AND >> > >> > A0.Obj='Uv::http://www.utdallas.edu/~farhan.husain/IngentaConnect/issue1_1' >> > AND A0.GraphID=1 AND A0.Subj=A1.Subj AND >> > A1.Prop='Uv::http://www.w3.org/1999/02/22-rdf-syntax-ns#type' AND >> > A1.Obj='Uv::http://metastore.ingenta.com/ns/structure/Article' AND >> > A1.GraphID=1 AND A0.Subj=A2.Subj AND >> > A2.Prop='Uv::http://prismstandard.org/namespaces/1.2/basic/startingPage' >> > AND >> > A2.GraphID=1; >> > >> > Table: >> > >> > Table "public.jena_g1t1_stmt" >> > Column | Type | Modifiers >> > ---------+-------------------- >> > ----+----------- >> > subj | character varying(250) | not null >> > prop | character varying(250) | not null >> > obj | character varying(250) | not null >> > graphid | integer | >> > Indexes: >> > "jena_g1t1_stmt_ixo" btree (obj) >> > "jena_g1t1_stmt_ixsp" btree (subj, prop) >> >> Isn't it missing an index on the column prop? >> >> select ... where A0.Prop='foo' and ... >> -- > Can you please elaborate a bit? I thought that A0.Prop would ignore the composite index created on the columns subj and prop but this does not seem to be the case. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
