Re: pgAdmin3 1.16 and 1.14 don't show Covering Index on Foreign Keys - Mailing list pgadmin-support

On Fri, 2012-08-03 at 21:06 +0300, Nikolay Ulyanitsky wrote:
> Hello
> 
> pgAdmin3 1.16 / 1.14 don't show "Covering Index" values on Foreign Keys.
> "Covering Index" values are always empty on "Properties" tab and
> have default values (fki-fk-*) on "Foreign Key" dialogs.
> 
> Tested pgAdmin3 versions with bug: 1.16.0 beta3, 1.14.3.
> 
> pgadmin3 1.12.3 doesn't have this bug and shows covering indexes correctly.
> 
> PostgreSQL 9.1.4 x86_64
> CentOS 6.3 x86_64
> 
> See screenshots:
> * 1.12.3: http://s18.postimage.org/h1w5atycn/1_12_3.png
> * 1.16.0: http://s17.postimage.org/xud5yf2h9/1_16_0.png
> 
> 
> Example DB:
> 
> CREATE TABLE pkgs (
>   id serial NOT NULL,
>   ...
>   CONSTRAINT "pk-pkgs-id" PRIMARY KEY (id ),
> )
> 
> CREATE TABLE files (
>   id bigserial NOT NULL,
>   pkg_id integer NOT NULL,
>   dir character varying NOT NULL,
>   files character varying NOT NULL,
>   CONSTRAINT "pk-files-id" PRIMARY KEY (id ),
>   CONSTRAINT "fk-files-pkg_id" FOREIGN KEY (pkg_id)
>       REFERENCES pkgs (id) MATCH SIMPLE
>       ON UPDATE RESTRICT ON DELETE CASCADE
> )
> 
> 
> CREATE INDEX "ix-files-pkg_id" ON files USING btree (pkg_id);
> 
> 
> Please fix it.
> "Covering Index" is a very important feature.
> 

It took me a long time to find the culprit. Anyway, this is fixed in
1.16, and the dev branch.

Thanks for your report.


-- 
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com