| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Curt Sampson" <cjs(at)cynic(dot)net>, "Don Baccus" <dhogaza(at)pacifier(dot)com>, "Lamar Owen" <lamar(dot)owen(at)wgcr(dot)org>, "Greg Copeland" <greg(at)CopelandConsulting(dot)Net>, "PostgresSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Inheritance |
| Date: | 2002-08-14 04:47:17 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOAELBCDAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Right. Instead of talking in circles, let's figure out how to do it.
> If the issue is only sequence numbers, can we force a column to _only_
> get values from the sequence counter, thereby makeing the index span
> unnecessary? Can't we look up stuff in parent/child index to check for
> collisions before we add a row? Doesn't seem too hard to me.
Is it theoretically possible to add support to btree for storing table along
with the indexed value? This would obviously add overhead, so it would only
be done for spanning indexes. The index would also take up more space on
disk I guess.
When a new inherited table is created, all parent indices would be dropped
and recreated as spanning indices and vice versa.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-08-14 04:48:22 | Re: [HACKERS] tsearch vs. fulltextindex |
| Previous Message | Bruce Momjian | 2002-08-14 04:45:57 | Re: Open 7.3 items |