Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)
От | Pavel Stehule |
---|---|
Тема | Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767) |
Дата | |
Msg-id | 162867790712190129q22f34b8al7cb4a05d994ee665@mail.gmail.com обсуждение исходный текст |
Ответы |
Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0
rev 6766-6767)
|
Список | pgadmin-support |
Hello it's pgAdmin bug. please report it there Regards Pavel Stehule On 19/12/2007, Boonchai <boonchai@xsidekick.com> wrote: > > 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. > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend >
В списке pgadmin-support по дате отправления: