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

From: NikhilS <nikkhils(at)gmail(dot)com>
To: "Dave Page" <dpage(at)postgresql(dot)org>
Cc: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, Boonchai <boonchai(at)xsidekick(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgadmin-support(at)postgresql(dot)org
Subject: Re: BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)
Date: 2007-12-19 11:06:06
Message-ID: d3c4af540712190306u42db31e3w3f0ffc75ba1724aa@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support 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 Content-Type Size
pg_get_indexdef.patch text/x-patch 1.3 KB

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Tom Lane 2007-12-19 17:33:13 Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)
Previous Message Dave Page 2007-12-19 10:03:41 Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-12-19 15:25:36 Re: ltree installation error
Previous Message Zdenek Kotala 2007-12-19 10:45:28 Re: Bug (#3484) - Invalid page header again