From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
Cc: | pgsql-hackers(at)postgreSQL(dot)org, database(at)FreeBSD(dot)ORG |
Subject: | Re: [HACKERS] Re: Mysql 321 - Mysql 322 - msql |
Date: | 1998-12-01 23:27:41 |
Message-ID: | 199812012327.SAA07094@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I don't currently have any databases that could benefit from full-text
> indexes. But I can think of applications where it'd be important,
> particularly after we get rid of the limit on tuple sizes so that it
> becomes reasonable to put fair-size chunks of text into database
> entries. For example: would it be useful to put my email archive into
> a Postgres database, one message per tuple? Maybe ... but if I can't
> glimpse it afterwards, forgetaboutit.
>
> You could probably glue something like this together from existing
> spare parts, say by running a nightly cron job that dumps out the
> text fields of your database for indexing by Glimpse. But it wouldn't
> be integrated into SQL --- you'd have to query the index separately
> outside of SQL, then use the results to drive a query to fetch the
> selected records.
We do have contrib/fulltextindex.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Marcus Mascari | 1998-12-02 00:15:38 | Bug in 6.4 query of table in varchar.c |
Previous Message | Bruce Momjian | 1998-12-01 23:15:52 | Re: [HACKERS] 6.4.x |