Re: pg_migrator and an 8.3-compatible tsvector data type

From: Greg Stark <stark(at)enterprisedb(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Date: 2009-05-28 22:42:45
Message-ID: 4136ffa0905281542m3613907r47017e01ba303446@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 28, 2009 at 11:26 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Kind of --- I am stuck because we don't auto-cast for index usage like
> we do for function calls and operators, so I will just keep going and
> disable tsvector.

I was pretty stumped by what you meant by "auto-cast" but now I'm
beginning to think what you're looking for are cross-type comparison
operators? You could define a bunch of such operators which manually
call the cast on one side and add them to the operator class. I'm not
sure how to set up the operator class entries for GIN though.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-05-28 22:49:19 Re: User-facing aspects of serializable transactions
Previous Message Tom Lane 2009-05-28 22:28:14 Re: Dtrace probes documentation