| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Parameters of GiST indexes |
| Date: | 2010-06-06 14:24:03 |
| Message-ID: | AANLkTilybCC9tpa1j7xNluUo8U1g8lI2HVLkAv2a_F8g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers,
I found that some parameters of GiST implementation are builin in the code.
For example, following can be found in the backend/utils/adt/tsgistidx.c:
#define SIGLENINT 31 /* >121 => key will toast, so it will not
work
* !!! */
#define SIGLEN ( sizeof(int4) * SIGLENINT )
#define SIGLENBIT (SIGLEN * BITS_PER_BYTE)
I think that such parameters don't have optimal value for all the cases; and
it would be a great option to let user define such parameters for particular
index.
For example, following syntax can be used:
CREATE INDEX name ON table USING gist(column) WITH (SIGLENINT=63);
With best regards,
Korotkov Alexander.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2010-06-06 20:00:08 | Re: multibyte charater set in levenshtein function |
| Previous Message | Florian Pflug | 2010-06-06 12:41:21 | Re: PITR Recovery Question |