Re: tsearch_core patch: permissions and security issues - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: tsearch_core patch: permissions and security issues
Date
Msg-id 200706141821.l5EILjj14009@momjian.us
Whole thread Raw
In response to Re: tsearch_core patch: permissions and security issues  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: tsearch_core patch: permissions and security issues
List pgsql-hackers
I an attempt to communicate what full text search does, and what
features we are thinking of adding/removing, I have put up the
introduction in HTML:
http://momjian.us/expire/fulltext/HTML/fulltext-intro.html

The links to the other sections don't work yet.

---------------------------------------------------------------------------

Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
> > Well my argument has always been the "core" feature argument. Perhaps I 
> > am missing some info here, but when I read what you wrote, I read that 
> > Tsearch will now be "harder" to work with. Not easier. :(
> 
> Then you misread it.  What I was proposing was essentially that there
> won't be any need for pg_dump support because everything's built-in
> (at least as far as parsers/dictionaries go).
> 
> As for the permissions issues, that's just formalizing something that's
> true today with the contrib module: if you change a configuration, it's
> *your* problem whether that invalidates any table entries, the system
> won't take care of it for you.
> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

--  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: "Simon Riggs"
Date:
Subject: Re: Sorted writes in checkpoint
Next
From: Teodor Sigaev
Date:
Subject: Re: tsearch_core patch: permissions and security issues