From: Ottó Havasvölgyi <havasvolgyi.otto@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Throwing unnecessary joins away
Date: Thu, 12 Jan 2006 13:18:58 +0100
Message-ID: <34608c0c0601120418n1af567b9n@mail.gmail.com> (raw)
Hi all,
Is PostgreSQL able to throw unnecessary joins?
For example I have two tables, and I join then with their primary keys, say
type of bigint . In this case if I don't reference to one of the
tables anywhere except the join condition, then the join can be eliminated.
Or if I do a "table1 left join table2 (table1.referer=table2.id)" (N : 1
relationship), and I don't reference table2 anywhere else, then it is
unnecessary.
Primary key - primary key joins are often generated by O/R mappers. These
generated queries could be optimized even more by not joining if not
necessary.
You may say that I should not write such queries. The truth is that the O/R
mapper is generating queries on views, and it does not use every field every
time, but even so the query of the view is executed with the same plan by
PostgreSQL, although some joins are unnecessary.
So basically this all is relevant only with views.
Best Regards,
Otto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: havasvolgyi.otto@gmail.com
Subject: Re: Throwing unnecessary joins away
In-Reply-To: <34608c0c0601120418n1af567b9n@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox