On Wed, Sep 29, 2010 at 1:29 AM, Sushant Sinha <sushant...@gmail.com> wrote: > Any updates on this? > > > On Tue, Sep 21, 2010 at 10:47 PM, Sushant Sinha <sushant...@gmail.com> > wrote: >> >> > I looked at this patch a bit. I'm fairly unhappy that it seems to be >> > inventing a brand new mechanism to do something the ts parser can >> > already do. Why didn't you code the url-part mechanism using the >> > existing support for compound words? >> >> I am not familiar with compound word implementation and so I am not sure >> how to split a url with compound word support. I looked into the >> documentation for compound words and that does not say much about how to >> identify components of a token. Does a compound word split by matching >> with a list of words? If yes, then we will not be able to use that as we >> do not know all the words that can appear in a url/host/email/file.
It seems to me that you need to familiarize yourself with this stuff and then post an analysis, or a new patch. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
