On Fri, Feb 10, 2017 at 2:28 PM, Robert Haas <robertmh...@gmail.com> wrote:
> On Thu, Feb 9, 2017 at 7:37 PM, Andres Freund <and...@anarazel.de> wrote: > > On 2017-02-09 19:19:21 -0500, Stephen Frost wrote: > >> * Robert Haas (robertmh...@gmail.com) wrote: > >> > On Thu, Feb 9, 2017 at 4:24 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > >> > > Also, our experience with contrib/tsearch2 suggests that the > extension > >> > > shouldn't be part of contrib, because we have zero track record of > getting > >> > > rid of stuff in contrib, no matter how dead it is. > >> > > >> > Let's nuke tsearch2 to remove this adverse precedent, and then add the > >> > new thing. > >> > > >> > Anybody who still wants tsearch2 can go get it from an old version, or > >> > somebody can maintain a fork on github. > >> > >> Works for me. > > > > +1 > > OK, that's three votes in favor of removing tsearch2 (from core, > anyone who wants it can maintain a copy elsewhere). Starting a new > thread to make sure we collect all the relevant votes, but I really, > really think it's past time for this to go away. The last actual > change to tsearch2 which wasn't part of a wider cleanup was > 3ca7eddbb7c4803729d385a0c9535d8a972ee03f in January 2009, so it's been > 7 years since there's been any real work done on this -- and the > release where we brought tsearch into core is now EOL, plus three more > releases besides. > +1 ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
