This seems to me to be an expensive plan and I'm wondering if there's a
way to improve it or a better way to do what I'm trying to do here (get
a count of distinct values for each record_id and map that value to the
entity type) entity_type_id_mapping is 56 rows
volume_node_entity_data_values is
How is it that the index scan has such poor performance? Shouldn't index
lookups be quicker?
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 26, 2005 1:32 PM
To: Brad Might
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Specific
I am seeing vastly different performance characteristics for almost the
exact same query.
Can someone help me break this down and figure out why the one query
takes so much longer than the other?
Looking at the explain analyze output, I see that the loops value on the
innermost index scan when bu
o:[EMAIL PROTECTED]
Sent: Thursday, May 26, 2005 1:32 PM
To: Brad Might
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Specific query performance problem help requested
- postgresql 7.4
"Brad Might" <[EMAIL PROTECTED]> writes:
> Can someone help me break this
I am seeing vastly different performance characteristics for almost the
exact same query.
Can someone help me break this down and figure out why the one query
takes so much longer than the other?
Looking at the explain analyze output, I see that the loops value on the
innermost index scan when b