Re: Re: [HACKERS] 8Ko limitation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jules Bean <jules(at)jellybean(dot)co(dot)uk>
Cc: Stephane Bortzmeyer <bortzmeyer(at)pasteur(dot)fr>, Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, pgsql-general(at)postgresql(dot)org
Subject: Re: Re: [HACKERS] 8Ko limitation
Date: 2000-07-20 14:52:49
Message-ID: 24680.964104769@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Jules Bean <jules(at)jellybean(dot)co(dot)uk> writes:
>> A colleague told me to use NetBSD instead, because PostgreSQL on a
>> Linux machine cannot host more than 2 Gb per database. Any practical
>> experience? (I'm not interested in "It should work".)

> Postgres splits large tables into multiple files.

Segmenting into multiple files used to have some bugs, but that was a
few versions back --- I think your colleague's experience is obsolete.
There are lots of people using multi-gig tables now.

It's presently still painful to manage a database that spans multiple
disks, however. (You can do it if you're willing to move files around
and establish symlinks by hand ... but it's painful.) There are plans
to make this better, but for now you might want to say that the
practical limit is the size of disk you can buy. Alternatively, if
your OS can make logical filesystems that span multiple disks, you
can get around the problem that way.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alex Bolenok 2000-07-20 14:54:19 Re: Re: Migrating from MS SQL server
Previous Message Tom Lane 2000-07-20 14:25:07 Re: unique constraint - bug?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-07-20 14:58:43 Re: Hello PL/Python
Previous Message Jan Wieck 2000-07-20 14:23:01 PGLZ memory problems fixed