Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: Mysql 321 - Mysql 322 - msql

From: Tom Ivar Helbekkmo <tih(at)nhh(dot)no>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org, database(at)FreeBSD(dot)ORG
Subject: Re: [HACKERS] Re: Mysql 321 - Mysql 322 - msql
Date: 1998-11-27 19:20:16
Message-ID: 861zmpj633.fsf@athene.nhh.no (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> 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.

Another very important application is the keeping of structured
documents in a database system.  Advanced SGML environments do this,
and Philip Greenspun of MIT, the author of the excellent book
"Database Backed Web Sites" (see http://photo.net/ for information)
recommends doing it for HTML and other data for web publishing.  The
web server AOLserver is just one example of an application that can do
this -- and if I'm not mistaken, AOLserver can even use PostgreSQL.

Anyway, once the data is in the database, and much of it is text, it
becomes very interesting to be able to efficiently index and search.

-tih
-- 
Popularity is the hallmark of mediocrity.  --Niles Crane, "Frasier"

In response to

pgsql-hackers by date

Next:From: Jan WieckDate: 1998-11-27 21:17:46
Subject: redolog - for discussion
Previous:From: Tom LaneDate: 1998-11-27 19:16:33
Subject: Re: [HACKERS] copy

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group