Re: BUMP: Using foreign key constraint to eliminate unnecessary joins in view - Mailing list pgsql-general

From Jaime Casanova
Subject Re: BUMP: Using foreign key constraint to eliminate unnecessary joins in view
Date
Msg-id 3073cc9b0904131509n3e95e908raf40e3a6216247cd@mail.gmail.com
Whole thread Raw
In response to BUMP: Using foreign key constraint to eliminate unnecessary joins in view  (Paul Wehr <sf_psql_general@informationsoftworks.com>)
List pgsql-general
On Mon, Apr 13, 2009 at 2:36 PM, Paul Wehr
<sf_psql_general@informationsoftworks.com> wrote:
>
> I am looking for a way to get the plan to show only a seq scan of test2,
> since test1 does not contribute any columns, and we know from the
> not-deferrable-not-null-primary-key that there will always be exactly one
> match.
>
> Am I just missing something obvious, or does postgresql (currently) not do
> that?
>

postgres will look at all tables involved, i think there is work to
make it smart enough to make what you describe but that's in the
future...


--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: "PostgreSQL in the cloud" now up on media.postgresql.org
Next
From: Tom Lane
Date:
Subject: Re: BUMP: Using foreign key constraint to eliminate unnecessary joins in view