Tom Lane t...@sss.pgh.pa.us wrote on 10-03-2010 23:37:20:
Tom Lane t...@sss.pgh.pa.us
10-03-2010 23:37
Right now, nodeNestloop is not really aware of whether the inner scan
depends on any parameters from the outer scan, so it's a bit hard to
determine whether the join can be abandoned.
Hi group,
We have two related tables with event types and events. We query for a join
between these two tables and experience that, when there is an
to-be-expected very small result set, this query performs particularly
poor. Understanding in this matter would be appreciated.
SELECT * from
Hi group,
We have two related tables with event types and events. We query for a join
between these two tables and experience that, when there is an
to-be-expected very small result set, this query performs particularly
poor. Understanding in this matter would be appreciated.
SELECT * from
Hi folks,
We have two related tables with event types and events. We query for a join
between these two tables and experience that, when there is an
to-be-expected very small result set, this query performs particularly
poor. Understanding in this matter would be appreciated.
SELECT * from
Hello Sander,
Can you post the explain plan output of these queries?
SELECT * FROM events_events LEFT OUTER JOIN events_event_types ON
eventType_id=events_event_types.id WHERE severity=20 AND (eventType_id
IN (71)) ORDER BY datetime DESC limit 50;
SELECT * FROM events_events LEFT OUTER JOIN
Hi,
EXPLAIN SELECT * FROM events_events LEFT OUTER JOIN events_event_types ON
eventType_id=events_event_types.id WHERE severity=20 AND (eventType_id
IN (71)) ORDER BY datetime DESC limit 50;
QUERY PLAN
sverha...@wps-nl.com wrote:
Hi,
EXPLAIN SELECT * FROM events_events LEFT OUTER JOIN events_event_types ON
eventType_id=events_event_types.id WHERE severity=20 AND (eventType_id
IN (71)) ORDER BY datetime DESC limit 50;
QUERY PLAN
Thanks - I'm sorry that I was not more specific earlier, but what would
be *really* helpful is the output of explain analyze, since that also
shows actual time, # rows and # loops of the inner nestloop.
No problem at all.
EXPLAIN ANALYZE SELECT * FROM events_events LEFT OUTER JOIN
sverha...@wps-nl.com wrote:
Thanks - I'm sorry that I was not more specific earlier, but what would
be *really* helpful is the output of explain analyze, since that also
shows actual time, # rows and # loops of the inner nestloop.
No problem at all.
EXPLAIN ANALYZE SELECT * FROM
In article
of6136ad9b.d40f3af5-onc12576e2.002d5763-c12576e2.002fb...@imtechrelay.nl,
sverha...@wps-nl.com writes:
SELECT * FROM events_events LEFT OUTER JOIN events_event_types ON
eventType_id=
events_event_types.id WHERE severity=70 AND (eventType_id IN (71)) ORDER BY
datetime DESC LIMIT
Robert Haas robertmh...@gmail.com writes:
It does seem like once the materialize step is done we could notice
that the tuplestore is empty and, given that uses no outer variables
or parameters and therefore will never be re-executed, we could skip
the rest of the index scan.
Yeah, the same
11 matches
Mail list logo
