From: | ohp(at)pyrenet(dot)fr |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | index as large as table |
Date: | 2005-08-20 12:18:29 |
Message-ID: | Pine.UW2.4.53.0508201413430.7116@sun.pyrenet |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
While testing 8.1dev I came to this:
CREATE TABLE t (
a int,
b int
PRIMARY KEY (a,b));
In that case, the index is as big as the table.
My question is is it worthwhile to have such index peformance wise.
I understand I'd loose uniqness buthas such an index any chance to be used
against seq scan.
Is there any chance we have a "btree table" in the future for that case?
Regards,
--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: ohp(at)pyrenet(dot)fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Stone | 2005-08-20 12:18:33 | Re: extremly low memory usage |
Previous Message | Michael Stone | 2005-08-20 12:15:04 | Re: Query plan looks OK, but slow I/O - settings advice? |