| From: | Peter Mount <peter(at)retep(dot)org(dot)uk> | 
|---|---|
| To: | Brian Piatkus <brian(at)brianp(dot)demon(dot)co(dot)uk> | 
| Cc: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: [GENERAL] Large Database & Indexes (Indices?) | 
| Date: | 2000-02-08 12:26:12 | 
| Message-ID: | Pine.LNX.4.10.10002081224550.5227-100000@maidast.retep.org.uk | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Tue, 8 Feb 2000, Brian Piatkus wrote:
> I am constructing a large ( by some standards) database where the largest table
> threatens to be about 6-10 Gb on a Linux system. I understand that postgresql
> splits the tables into manageable chunks & I have no problem with that as a
> workround for the 2 GB fs limit
> .. 	My question concerns the indexes ,the first of which looks to be  around 
> 40 % of the table size. How is this
> handled and how do I create subsequent indices on large tables given that I
> can't interrupt the process,  move and symbolically link chunks ?
IIRC Indices you the same storage manager as tables, so they should split
at the same intervals as tables (default is 1Gb). Someone correct me if
I'm wrong.
Peter
--
       Peter T Mount peter(at)retep(dot)org(dot)uk
      Main Homepage: http://www.retep.org.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
 Java PDF Generator: http://www.retep.org.uk/pdf
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian Piatkus | 2000-02-08 13:22:35 | Re: Large Database & Indexes (Indices?) | 
| Previous Message | Brian Piatkus | 2000-02-08 11:22:42 | Large Database & Indexes (Indices?) |