| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | gjerde(at)icebox(dot)org, PostgreSQL-development <hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] 6.5 TODO list |
| Date: | 1999-05-12 02:11:22 |
| Message-ID: | 199905120211.WAA02144@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I just got to thinking, what about indexes > 2GB? With my 3GB table one
> > of the index is 540MB. Both with growth I might get there. Does that
> > work and does it use RELSEG_SIZE?
>
> index_destroy in backend/catalog/index.c looks to be coping with only
> one segment file ... not sure why it doesn't go through md.c for this.
Added to Open Items:
Multi-segment indexes?
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-05-12 02:15:13 | Re: [HACKERS] 6.5 TODO list |
| Previous Message | Bruce Momjian | 1999-05-12 02:05:58 | Re: sequences vs. transactions |