Re: [HACKERS] Problems with >2GB tables on Linux 2.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "D'Arcy" "J(dot)M(dot)" Cain <darcy(at)druid(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Problems with >2GB tables on Linux 2.0
Date: 1999-02-08 03:04:22
Message-ID: 13830.918443062@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"D'Arcy" "J.M." Cain <darcy(at)druid(dot)net> writes:
> Thus spake Tom Lane
>> I'd suggest setting the limit a good deal less than 2Gb to avoid any
>> risk of arithmetic overflow. Maybe 200000 8K blocks, instead of 262144.

> Why not make it substantially lower by default?

Configure-time option, anyone ;-) ?

> Makes it easier to split
> a database across spindles. Even better, how about putting extra extents
> into different directories like data/base.1, data/base.2, etc?

This could be a pretty good idea. Right now, if you need to split a
database across multiple filesystems, you have to do a bunch of tedious
hand manipulation of symlinks. With an option like this, you could
automatically distribute your larger tables across filesystems...
set up the subdirectories as symlinks once, and forget it...

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-02-08 03:07:35 Re: [HACKERS] Problems with >2GB tables on Linux 2.0
Previous Message Bruce Momjian 1999-02-08 02:53:20 Re: [HACKERS] trouble with rules