Re: [pgadmin-support] text_pattern_ops not shown in index command

[Dave Page]

Andrus wrote:

To reproduce:

create table foo ( bar char(20));
CREATE UNIQUE INDEX bar_pattern_idx ON foo(LOWER(bar) text_pattern_ops);

Observed in pgAdmin 1.6 post beta-1 table definition pane:

CREATE UNIQUE INDEX bar_pattern_idx
  ON foo
  USING btree
  (lower(bar::text));

Expected:

text_pattern_ops must be present

Thanks, fixed in SVN.

Regards, 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