Re: tsearch2 patch status report

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Magnus Hagander" <magnus(at)hagander(dot)net>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>, "Teodor Sigaev" <teodor(at)sigaev(dot)ru>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: tsearch2 patch status report
Date: 2007-08-22 01:24:02
Message-ID: b42b73150708211824k19ad9065qbd708a824ab413d6@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/21/07, Magnus Hagander <magnus(at)hagander(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-08-22 01:26:42 Is ALTER TEXT SEARCH CONFIGURATION PARSER = new_parser really sane?
Previous Message Chad Wagner 2007-08-22 00:10:37 Re: tsearch2 patch status report