Re: Foreing Key / Unique Contraint indexes

Dave,
Cheers for the swift reply

Please refer to my comments below

/Jona

Dave Page wrote:

>
>
>
>
>>-----Original Message-----
>>From: pgadmin-support-owner(at)postgresql(dot)org
>>[mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of Jona
>>Sent: 09 June 2005 11:00
>>To: pgadmin-support(at)postgresql(dot)org
>>Subject: [pgadmin-support] Foreing Key / Unique Contraint indexes
>>
>>Hey
>>I'm unable to see the indexes for foreign keys and unique
>>constraints on
>>my tables, all other indexes are showing up fine in the table tree.
>>
>>
>
>Do you mean Primary keys?
>
>
Looking at the table tree again it seems that only "true" indexes are
displayed, seem to recall that in a previous version of pgAdmin Primary
keys were shown as well?

>
>
>>Am running pgAdmin 3, 1.3.0 from May 20th 2005 up against either a
>>PostGre 7.3.9 on Linux or a PostGre 8.0.3 on a Windows 2000 server.
>>
>>
>
>I'm guessing you mean PostgreSQL ? :-)
>
>
Ye, you got it! ;-)

>
>
>>Is the issue in pgAdmin (that it doesn't show the indexes for some
>>reason) or in PostGreSQL (that it doesn't create the indexes
>>eventhough
>>it says it does) ??
>>
>>
>
>pgAdmin hides indexes that implement other types of object. The fact
>that a unique constraint or a pkey is actually an index is an
>implementation detail and is unimportant to the user, in the same way
>that it is unimportant to show foreign keys as sets of triggers and
>views as rules as they really are.
>
>
Hmm... don't know if I agree with you here. I for one (as a user of a
great program) would like to know at least that an index is created for
the foreign key, primary key and unique constraint.
Especially because I've noticed that PostGreSQL seems to indexes on
foreign keys and unique constraints? But if you create another index on
the same column it suddenly starts using that.
Go figure....

>Regards, Dave.
>
>---------------------------(end of broadcast)---------------------------
>TIP 8: explain analyze is your friend
>
>