From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Mark Cave-Ayland" <m(dot)cave-ayland(at)webbased(dot)co(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: GiST: Need ideas on how to minimise data in a GiST index |
Date: | 2003-03-24 16:27:03 |
Message-ID: | 16818.1048523223@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"Mark Cave-Ayland" <m(dot)cave-ayland(at)webbased(dot)co(dot)uk> writes:
> This sounds exactly as if it would solve the problem. Have you got any
> pointers to documentation on this, and more specifically on the
> PostgreSQL implementation of GiST? (I'm guessing this is a GiST only
> extension). Has it been available since PostgreSQL 7.1 aswell?
No, lossiness is a generic index property. There's been some level of
support for it since Berkeley days, although we improved the flexibility
in 7.2 --- we now think of lossiness as a property associated with
specific operators rather than a whole index. That would probably not
matter for this particular situation, since you'd be wanting to mark all
the operators lossy anyway.
You can read about this stuff in the PG Programmer's Guide,
"Interfacing Extensions To Indexes". I'd start with the 7.3 version
and then work backwards.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-03-24 16:30:06 | Re: alter table change type column |
Previous Message | Mark Cave-Ayland | 2003-03-24 16:17:01 | Re: GiST: Need ideas on how to minimise data in a GiST index |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-03-24 16:28:15 | Re: PQescapeBytea on Win32 |
Previous Message | Mark Cave-Ayland | 2003-03-24 16:17:01 | Re: GiST: Need ideas on how to minimise data in a GiST index |