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

Re: [HACKERS] Re: yet another problem in recent builds, GIST this time

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: hannu(at)trust(dot)ee (Hannu Krosing)
Cc: selkovjr(at)mcs(dot)anl(dot)gov, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: yet another problem in recent builds, GIST this time
Date: 1998-10-11 17:07:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> "Gene Selkov, Jr." <selkovjr(at)mcs(dot)anl(dot)gov> wrote:
> > 
> > I think I have another problem similar to what I just reported. This time it is in GiST. It does not
> > complain when it builds the index but any attempt to use the table with exesisting GiST indices causes
> > this error:
> You seem to be the only one who actually uses GiST <grin>

See manuals.  There is a web site for gist.

> During last 2-3 years I have posted the question about the usability
> of GiST indexes to various Postgres lists about 3 times with absolutely 
> no reaction, so assumed that they didn't work at all ;(
> Could you point me to any information (FAQs, TFMs, ...) about their
> usage ?
> I have been under an impression that the easiest way of adding new 
> indexing strategies (I personally need full-text) to postgres would
> be thru GiST, but as I have had no luck in getting them to waork as 
> they were, I assumed that they were in fact unsupported remnants of 
> a long-forgotten project.

Full text can now be done with the new /contrib/fulltextindex functions.

  Bruce Momjian                        |
  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


pgsql-hackers by date

Next:From: Marc Howard ZuckmanDate: 1998-10-11 17:10:41
Subject: Re: [HACKERS] backslash in psql output
Previous:From: Bruce MomjianDate: 1998-10-11 17:06:14
Subject: Re: [HACKERS] Error messages crash backend

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