Skip site navigation (1) Skip section navigation (2)

Re: Are Indices automatically generated for primary keys?

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Thom Brown <thom(at)linux(dot)com>
Cc: Justin Graf <justin(at)magwerks(dot)com>, Kevin(dot)Grittner(at)wicourts(dot)gov, depesz(at)depesz(dot)com, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Are Indices automatically generated for primary keys?
Date: 2010-08-25 06:58:59
Message-ID: 4C74BF33.3080901@lelarge.info (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-performance
Le 18/08/2010 17:23, Thom Brown a écrit :
> On 18 August 2010 17:06, Justin Graf <justin(at)magwerks(dot)com> wrote:
>> On 8/18/2010 9:15 AM, Clemens Eisserer wrote:
>>> Hi,
>>>
>>>
>>>> they are generated automatically.
>>>>
>>> Thanks depesz!
>>> The reason why I asked was because pgAdmin doesn't display the
>>> automatically created indices, which confused me.
>>>
>>> Thanks, Clemens
>>>
>> PGAdmin caches all database layout locally, the tree view can get very
>> stale.  So refresh the treeview with either F5 or right click an item in
>> the treeview click refresh to rebuild the list.
>>
> 
> I don't think PgAdmin will display indexes created by primary keys,
> only if indisprimary is false.
> 

pgAdmin doesn't display indexes for primary keys and unique constraints.
These objects are already displayed in the constraints nodes. The fact
that they use an index to enforce the constraints is an implementation
detail.


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com

In response to

pgsql-performance by date

Next:From: Bob LunneyDate: 2010-08-25 14:30:31
Subject: Re: Triggers or code?
Previous:From: Jann RöderDate: 2010-08-24 13:24:30
Subject: Re: Inefficient query plan

pgsql-general by date

Next:From: Guy RouillierDate: 2010-08-25 07:03:11
Subject: Re: IBATIS support for postgres cursors
Previous:From: Alban HertroysDate: 2010-08-25 06:22:34
Subject: Re: Win32 Backend Cash - pre-existing shared memory block is still in use

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group