BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767) - Mailing list pgsql-bugs

From Boonchai
Subject BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)
Date
Msg-id 200712190719.lBJ7JAXU090001@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      3829
Logged by:          Boonchai
Email address:      boonchai@xsidekick.com
PostgreSQL version: 8.3 beta 4
Operating system:   windows XP
Description:        Wrong index reporting from pgAdmin III (v1.8.0 rev
6766-6767)
Details:

I created a table by

CREATE TABLE test_desc
(
  id integer,
  f1 character(10),
  f2 character(20)
)

case 1 :
Created index by

CREATE INDEX test_desc_idx1
  ON test_desc
  USING btree
  (f1, f2 desc)

but pgAdmin reported like this

CREATE INDEX test_desc_idx
  ON test_desc
  USING btree
  (f1 DESC, f2 DESC)


case 2:
Created another index by

CREATE INDEX test_desc_idx2
  ON test_desc
  USING btree
  (f1 desc, f2);

but pgAdmin reported

CREATE INDEX test_desc_idx2
  ON test_desc
  USING btree
  (f1 DESC,  DESCf2);

Anyway, these 2 indexes are corrected, seen from pg_indexes.

pgsql-bugs by date:

Previous
From: dhliu
Date:
Subject: SELECT LIKE 'xxx%' doesn't use index scan
Next
From: "Pavel Stehule"
Date:
Subject: Re: SELECT LIKE 'xxx%' doesn't use index scan