Re: text search vs schemas

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, Trevor Talbot <quension(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: text search vs schemas
Date: 2007-08-17 14:42:09
Message-ID: 5324.1187361729@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> On Fri, Aug 17, 2007 at 01:16:22AM -0400, Tom Lane wrote:
>> That seems like it'd fix the problem for expression indexes on
>> to_tsvector calls, but I don't see how it fixes the problem for
>> triggers. We don't have any clear path for making trigger arguments
>> be anything but a list of strings.

> I'm unsure how it works now, but it seems reasonable that when a
> regclass/regtype/regetc is passed to a trigger, pass it in OID form.

If you insist on a solution that involves attaching type information
to trigger arguments, then we can forget about getting tsearch into 8.3.
That's a nontrivial amount of new design and code that hasn't even been
on the radar screen before.

At the moment I feel our thoughts have to revolve not around adding
complexity to tsearch, but taking stuff out. If we ship it with no
schema support for TS objects in 8.3, we can always add that later,
if there proves to be real demand for that (and I note that the contrib
version has gotten along fine without it). But we cannot go in the
other direction.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-08-17 14:58:28 Re: tsearch2 in PostgreSQL 8.3?
Previous Message Robert Treat 2007-08-17 14:35:50 Re: tsearch2 in PostgreSQL 8.3?