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

From Simon Riggs
Subject Re: tsearch_core patch: permissions and security issues
Date
Msg-id 1181921976.17734.14.camel@silverbirch.site
Whole thread Raw
In response to Re: tsearch_core patch: permissions and security issues  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 2007-06-15 at 10:36 -0400, Tom Lane wrote:
> "Simon Riggs" <simon@2ndquadrant.com> writes:
> > Although I'm happy to see tsearch finally hit the big time, I'm a bit
> > disappointed to see so many new datatype-specific SQL commands created.
> 
> Per subsequent discussion we are down to just one new set of commands,
> CREATE/ALTER/DROP TEXT SEARCH CONFIGURATION, so it's not as big a
> footprint as it was to start with.

Thats a lot better, thanks. I'm sure that will work better in PgAdmin
and many other places too.

> I have been thinking that it would be smart to try to use the generic
> "definition list" syntax, like CREATE OPERATOR and CREATE AGGREGATE.
> But the motivation for that is just to avoid defining more keywords
> (which has an overall impact on parser size and performance).  It's
> not really going to do anything for us in terms of having an
> implementation that can be shared with anything else.

It's OK; ALTER RFID TAG NOMENCLATURE has a nice ring to it. :-)

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: How does the tsearch configuration get selected?
Next
From: Teodor Sigaev
Date:
Subject: Re: How does the tsearch configuration get selected?