I could be wrong, but I would swear I was once able to set up my foreign
key constraints so that the optimizer would not bother looking up rows in
tables that did not contribute to the result set. This is useful because I
can set up a single view that joins all the related tables together, but
ca
un, 29 Mar 2009 14:00:53 -0400
From: Paul Wehr
To: pgsql-general@postgresql.org
I could be wrong, but I would swear I was once able to set up my foreign
key constraints so that the optimizer would not bother looking up rows in
tables that did not contribute to the result set. This is useful because
Summary: Proposed solution, and question on efficiency of technique
I don't know if this is what you are looking for, but I have a database where
I needed a relatively complex view (which I can do thanks to the expanded view
buffer in 7.0!, it didn't fit in 6.5.3), but I need to pass an "effecti
