Re: tsearch_core patch: permissions and security issues

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Teodor Sigaev <teodor(at)sigaev(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Subject: Re: tsearch_core patch: permissions and security issues
Date: 2007-06-15 15:06:22
Message-ID: 200706151106.23423.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

On Thursday 14 June 2007 15:10, Teodor Sigaev wrote:
> That changes are doable for several days. I'd like to make changes together
> with replacing of FULLTEXT keyword to TEXT SEARCH as you suggested.

AIUI the discussion on this change took place off list? Can we get a preview
of what the commands will look like and maybe a summary of the discussion? It
may sound a bit pedantic, but the concept/wording of "full text searching" is
pretty well understood by the database community, so switching to just TEXT
SEARCH sounds like we're adding ambiguity for reasons that escape me....

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Teodor Sigaev 2007-06-15 15:15:16 Re: How does the tsearch configuration get selected?
Previous Message Tom Lane 2007-06-15 15:05:06 Re: How does the tsearch configuration get selected?

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2007-06-15 15:15:16 Re: How does the tsearch configuration get selected?
Previous Message Tom Lane 2007-06-15 15:05:06 Re: How does the tsearch configuration get selected?