Re: tsearch2 patch status report - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: tsearch2 patch status report
Date
Msg-id b42b73150708211824k19ad9065qbd708a824ab413d6@mail.gmail.com
Whole thread Raw
In response to Re: tsearch2 patch status report  (Magnus Hagander <magnus@hagander.net>)
Responses Re: tsearch2 patch status report  (Ron Mayer <rm_pg@cheapcomplexdevices.com>)
List pgsql-hackers
On 8/21/07, Magnus Hagander <magnus@hagander.net> wrote:
> OTOH, if we do it as a compat package, we need to set a firm end-date on
> it, so we don't have to maintain it forever. Given the issues always at
> hand for doing such an upgrade, my vote is actually for ripping it out
> completely and take the migration pain once and then be done with it.

I would suggest making a pgfoundry project...that's what was done with
userlocks.  I'm pretty certain no one besides me has ever used the
wrappers I created...a lot more people use tsearch2 than userlocks
though.

merlin


pgsql-hackers by date:

Previous
From: "Chad Wagner"
Date:
Subject: Re: tsearch2 patch status report
Next
From: Tom Lane
Date:
Subject: Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane?