From: | "Boonchai" <boonchai(at)xsidekick(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767) |
Date: | 2007-12-19 07:19:10 |
Message-ID: | 200712190719.lBJ7JAXU090001@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support pgsql-bugs |
The following bug has been logged online:
Bug reference: 3829
Logged by: Boonchai
Email address: boonchai(at)xsidekick(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2007-12-19 09:29:33 | Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767) |
Previous Message | Dave Page | 2007-12-17 09:11:47 | Re: pgAdmin III Bug Report |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2007-12-19 09:26:39 | Re: SELECT LIKE 'xxx%' doesn't use index scan |
Previous Message | iuri de araujo sampaio | 2007-12-19 06:48:33 | Re: ltree installation error |