Re: constraint with reference to the same table
Rudi Starcevic <rudi@oasis.net.au>
From: Rudi Starcevic <rudi@oasis.net.au>
To:
Cc: Postgres Performance <pgsql-performance@postgresql.org>
Date: 2003-05-15T02:29:22Z
Lists: pgsql-performance
Victor, >> You don't need it. Primary key on that 2 columns will create a unique index >> on them. Of course, if you left things unchanged - you'll need to create >> business_people index yourself. Ahh of course .. "I see said the blind man !" .. Thanks heaps. I think now it's pretty clear to me. I feel I have pretty much optimised my code / sql schema. Thank you both, it's a tremendous help - one learns something every day with this list. Kind regards Rudi. Victor Yegorov wrote: >* Rudi Starcevic <rudi@oasis.net.au> [15.05.2003 05:15]: > > >>Perhaps I also need a 3rd Index ? >> >>One for Business's >>One for People and >>One for Business_People. >> >>I think I may need the 3rd Index for query's like >> >> > >You don't need it. Primary key on that 2 columns will create a unique index >on them. Of course, if you left things unchanged - you'll need to create >business_people index yourself. > >execute: > >=> \d business_people > >and take a glance on a line, describing primary key. > > >