Re: tsearch still has external configuration files - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: tsearch still has external configuration files
Date
Msg-id 200708171735.l7HHZMQ25587@momjian.us
Whole thread Raw
In response to tsearch still has external configuration files  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> A couple months ago I wrote:
> > Lastly, I'm unhappy that the patch still keeps a lot of configuration
> > information, such as stop word lists, in the filesystem rather than the
> > database.  It seems to me that the single easiest and most useful part
> > of a configuration to change is the stop word list; but this setup
> > guarantees that no one but a DBA can do that, and what's more that
> > pg_dump won't record your changes.  What's the point of having any
> > non-superuser configuration capability at all, if stop words aren't part
> > of what you can change?
> 
> It appears that nothing has been done about this objection in the
> current patch.  It is too late to redesign stop word handling for 8.3,

Yes, I thought we agreed that for 8.3 we would use external files with
UTF8 encoding.

> BTW, I'm inclined to rename the installation directory to
> $SHAREDIR/tsearch_data/ ... any objections to that?

Seems clear to me.

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: tsearch2 in PostgreSQL 8.3?
Next
From: "Merlin Moncure"
Date:
Subject: pgparam extension to the libpq api