From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_get_INDEXdef - opclass |
Date: | 2006-06-12 11:13:45 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E401388881@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bah, I mean pg_get_indexdef of course :-)
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Dave Page
> Sent: 12 June 2006 12:12
> To: pgsql-hackers(at)postgresql(dot)org
> Subject: [HACKERS] pg_get_viewdef - opclass
>
> Following a pgAdmin bug report, I noticed that pg_get_viewdef doesn't
> return the opclass when called for a specific column (in 8.1
> at least) -
> for example, for the index:
>
> CREATE UNIQUE INDEX bar_pattern_idx2 ON foofoo USING btree
> (lower((bar)::text) bpchar_pattern_ops, bar2)
>
> A query on column 1 returns:
>
> lower((bar)::text)
>
> It seems to me that the opclass should be included as well.
>
> Regards, Dave.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org
> so that your
> message can get through to the mailing list cleanly
>
From | Date | Subject | |
---|---|---|---|
Next Message | Böszörményi Zoltán | 2006-06-12 12:27:31 | Re: Extended SERIAL parsing |
Previous Message | Dave Page | 2006-06-12 11:12:11 | pg_get_viewdef - opclass |