| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Indices for select count(*)? |
| Date: | 2005-12-23 18:38:29 |
| Message-ID: | 21985.1135363109@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> AFAICS two big problems with using an index type:
> 1. The index isn't told when the tuple is deleted.
Hm, good point ... we could make it do so but for ordinary deletes it'd
be a waste of cycles to open indexes at all.
> 2. The server expects to be able to lookup an index.
Only if there is a WHERE operator that matches the index's opclass.
This hypothetical index type would probably have one dummy opclass
containing no operators.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Adler | 2005-12-23 18:42:13 | Re: HINT: Perhaps out of disk space? |
| Previous Message | Martijn van Oosterhout | 2005-12-23 17:42:02 | Re: Indices for select count(*)? |