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

From NikhilS
Subject Re: BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)
Date
Msg-id d3c4af540712190306u42db31e3w3f0ffc75ba1724aa@mail.gmail.com
Whole thread Raw
In response to Re: BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)  (Dave Page <dpage@postgresql.org>)
Responses Re: BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi,
>> CREATE INDEX test_desc_idx1
>>   ON test_desc
>>   USING btree
>>   (f1, f2 desc)
>>
>> CREATE INDEX test_desc_idx2
>>   ON test_desc
>>   USING btree
>>   (f1 desc, f2);

postgres=# select pg_get_indexdef('test_desc_idx1'::regclass, 2, true);
 pg_get_indexdef
-----------------
 f2 DESC
(1 row)

postgres=# select pg_get_indexdef('test_desc_idx2'::regclass, 2, true);
 pg_get_indexdef
-----------------
 DESCf2
(1 row)

Looks like pg_get_indexdef is unwell :-(

yes, it was unwell in the area where the amcanorder was being processed. The attached patch should fix this.

Regards,
Nikhils
--
EnterpriseDB               http://www.enterprisedb.com
Attachment

pgsql-bugs by date:

Previous
From: Zdenek Kotala
Date:
Subject: Re: Bug (#3484) - Invalid page header again
Next
From: Tom Lane
Date:
Subject: Re: ltree installation error