From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "PostgreSQL-development"(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)postgreSQL(dot)org, Inoue(at)tpf(dot)co(dot)jp |
Subject: | Re: [HACKERS] tables > 1 gig |
Date: | 1999-06-17 15:10:34 |
Message-ID: | 4173.929632234@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
>> Then we'd better fix the underlying problem. We can't change
>> RELSEG_SIZE for a minor release, unless you want to give up the
>> principle of not forcing initdb at minor releases.
> Why can't we increase it?
Consider a 1.5-gig table. 6.5 will store it as one gig in file "table",
one-half gig in file "table.1". Now recompile with larger RELSEG_SIZE.
The file manager will now expect to find all blocks of the relation in
file "table", and will never go to "table.1" at all. Presto, you lost
a bunch of data.
Bottom line is just as it says in the config.h comments: you can't
change either BLCKSZ or RELSEG_SIZE without doing initdb.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-06-17 15:13:22 | Re: [HACKERS] tables > 1 gig |
Previous Message | Bruce Momjian | 1999-06-17 15:06:28 | Re: [HACKERS] tables > 1 gig |