CROSS JOIN performance - Mailing list pgsql-general

From Andy Chambers
Subject CROSS JOIN performance
Date
Msg-id CAAfW55o8Duta-GxHqc84AE=BMZOkJe6tPbANDWZjyb7mC0o2Zg@mail.gmail.com
Whole thread Raw
Responses Re: CROSS JOIN performance
List pgsql-general
Hi,

In our porting of a big mysql app to postgres, we're finding lots of
queries like

select foo
  from (foo f, bar b)
left join caz c on f.id = f.caz_id
where f.id = b.foo_id

I've seen the message where Tom explains why this is invalid in ANSI
SQL so I converted it to

select foo
  from foo f CROSS JOIN bar b
left join caz c on f.id = f.caz_id
where f.id = b.foo_id

...and it works.  However, sometimes quite slowly.  When we've looked
into the slow ones, we've found that changing it again to

select foo
  from foo f INNER JOIN bar b ON f.id = b.foo_id
left join caz c on f.id = f.caz_id

makes it perform much better.

Furthermore, we're starting to find that performance of the 3rd is
significantly better than the 2nd, *ONLY* when the CROSS JOINs are
followed by more joins (like in this case).  If there are no more
tables being joined, changing to the 3rd version yields no performance
gain.

Are these three queries logically equivalent (well, at least the
latter two since the first isn't valid SQL)?  If so, does it make
sense that the optimizer has difficulty with the second case.

Cheers,
Andy

--
Andy Chambers

pgsql-general by date:

Previous
From: sunpeng
Date:
Subject: Why warm-standby doesn't work using file-based log shipping method?
Next
From: Andre Lopes
Date:
Subject: How to store variable data in a field?