> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page
> Sent: 12 June 2006 12:13
> To: Andrus; pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] bpchar_pattern_ops not shown
> in index command
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Andrus
> > Sent: 06 June 2006 09:17
> > To: pgadmin-support@postgresql.org
> > Subject: [pgadmin-support] bpchar_pattern_ops not shown in
> > index command
> >
> > To reproduce, run:
> >
> > create table foo ( bar char(20));
> > CREATE UNIQUE INDEX bar_pattern_idx ON foo(LOWER(bar)
> > bpchar_pattern_ops);
> >
> >
> > Observed in pgadmin:
> >
> > CREATE UNIQUE INDEX bar_pattern_idx
> > ON foo
> > USING btree
> > (lower(bar::text));
>
> This appears to be an issue with the PostgreSQL function
> pg_get_indexdef
> - I've raised the issue on -hackers.
Apparently it was intended to work that way. SQL based fix committed to
trunk.
Thanks, Dave.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
