From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Chander Ganesan <chander(at)otg-nc(dot)com> |
Cc: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Questions about horizontal partitioning |
Date: | 2007-01-09 17:19:32 |
Message-ID: | 20070109171932.GC19523@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jan 09, 2007 at 08:28:29 -0500,
Chander Ganesan <chander(at)otg-nc(dot)com> wrote:
> It would. A query that uses an inner join implies that a matching entry
> must exist in both tables - so the join must occur, otherwise you could
> be returning rows that don't satisfy the join condition.
While this might not be worth doing, a foreign key constraint could be used
to establish the existance of the matching row, so that you wouldn't actually
need to look in the other table to verify that if you didn't need any of the
other columns in the other table. There will be some tricky cases for this,
such as when there are deferred constraints or when updating the foreign key
field.
From | Date | Subject | |
---|---|---|---|
Next Message | Rafal Pietrak | 2007-01-09 17:41:17 | Re: TRIGGER BEFORE INSERT |
Previous Message | Bruno Wolff III | 2007-01-09 17:11:26 | Re: SELECT INTO using Views? |