2GB file size limit

I'm pretty sure I remember one of the developers saying that postgres
works around this limit automatically by creating separate tables per
database/table/etc...

in other words it's not a problem. if I'm wrong, someone who knows
correct me.

-philip

On Mon, 21 May 2001, Thalis A. Kalfigopoulos wrote:

On Mon, May 21, 2001 at 09:31:13PM -0400, some SMTP stream spewed forth:

Hello all,
I upgraded from kernel 2.2.18 (Slakcware7.1 on x86) to 2.4.4 only to find out that I will still not get LFS due to my glibc2.1.3.
My question is the following: I know people have reported DBs larger than 2GB, but is there any single file that gets larger than 2GB? Can anyone make an estimate of what overall_DB_size will cause me to hit the 2GB-filesize limit?
Any ideas how to work around this other than upgrading glibc or changing OS or architecture? Having survived through Slackware evolution, I bet it'll be the last to adopt any changes in the field *sigh*

PostgreSQL works around the (ah hem) silly limits of
the (silly?) Linux kernel.
You could use FreeBSD and not worry about it all, or just not worry about
it at all---either way, it won't be a problem.

:)

gh

"Thalis A. Kalfigopoulos" <thalis@cs.pitt.edu> writes:

I upgraded from kernel 2.2.18 (Slakcware7.1 on x86) to 2.4.4
only to find out that I will still not get LFS due to my glibc2.1.3.
My question is the following: I know people have reported DBs larger
than 2GB, but is there any single file that gets larger than 2GB?
Can anyone make an estimate of what overall_DB_size will cause me to
hit the 2GB-filesize limit?

AFAIK, postgresql will split the tables across multiple files anyway
(Oracles does it, at least) - which is good for backups etc. That you
can create big files doesn't mean you want to.

--
Trond Eivind Glomsr�d
Red Hat, Inc.

On Mon, May 21, 2001 at 09:00:14PM -0500, GH wrote:

On Mon, May 21, 2001 at 09:31:13PM -0400, some SMTP stream spewed forth:

Hello all,
I upgraded from kernel 2.2.18 (Slakcware7.1 on x86) to 2.4.4 only
to find out that I will still not get LFS due to my glibc2.1.3.

PostgreSQL works around the (ah hem) silly limits of
the (silly?) Linux kernel.

Not a linux issue. he has to recompile glibc vs 2.4.x so that it knows
about large file support. then compile postgres against that.

I've done this with mysql and it works fine on a potato debian setup.

--
CaT (cat@zip.com.au) *** Jenna has joined the channel.
<cat> speaking of mental giants..
<Jenna> me, a giant, bullshit
<Jenna> And i'm not mental
- An IRC session, 20/12/2000

GH <grasshacker@over-yonder.net> writes:

PostgreSQL works around the (ah hem) silly limits of the (silly?)
Linux kernel.

As he wrote, it isn't a limit of the Linux kernel - it's a limit of
his glibc. FTR, there are also patches for the 2.2 kernel to handle
large files - our 6.2 Enterprise Edition shipped with that.

--
Trond Eivind Glomsr�d
Red Hat, Inc.

On Mon, May 21, 2001 at 09:31:13PM -0400, Thalis A. Kalfigopoulos wrote:

Hello all,
I upgraded from kernel 2.2.18 (Slakcware7.1 on x86) to 2.4.4 only to find out that I will still not get LFS due to my glibc2.1.3.
My question is the following: I know people have reported DBs larger than 2GB, but is there any single file that gets larger than 2GB? Can anyone make an estimate of what overall_DB_size will cause me to hit the 2GB-filesize limit?

Postgres splits table files after 1GB, so the file size limit shouldn't
affect the maximum table size. I'm not sure what the other limits are,
though. My guess is you can probably make as large a database as you
have the storage space for.

Cheers,

Neil

On Mon, May 21, 2001 at 10:09:01PM -0400, some SMTP stream spewed forth:

GH <grasshacker@over-yonder.net> writes:

PostgreSQL works around the (ah hem) silly limits of the (silly?)
Linux kernel.

As he wrote, it isn't a limit of the Linux kernel - it's a limit of
his glibc. FTR, there are also patches for the 2.2 kernel to handle
large files - our 6.2 Enterprise Edition shipped with that.

So I read.
Foot in mouth.
I apologize.

gh

You don't need large files. Postgres will use multiple
files for large tables.

"OIDs" are 32-bit integers. You can "only" have 2^^32
records in your database. This is a hard limit last I
checked. Don't know of anyone hitting it yet. I may
in a couple years but am not close yet.

-----Original Message-----
From: Thalis A. Kalfigopoulos [mailto:thalis@cs.pitt.edu]
Sent: Monday, May 21, 2001 6:31 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] 2GB file size limit

Hello all,
I upgraded from kernel 2.2.18 (Slakcware7.1 on x86) to
2.4.4 only to find out that I will still not get LFS due to
my glibc2.1.3.
My question is the following: I know people have
reported DBs larger than 2GB, but is there any single file
that gets larger than 2GB? Can anyone make an estimate of
what overall_DB_size will cause me to hit the 2GB-filesize limit?
Any ideas how to work around this other than upgrading
glibc or changing OS or architecture? Having survived through
Slackware evolution, I bet it'll be the last to adopt any
changes in the field *sigh*

thanks in advance,
thalis

---------------------------(end of
broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

This email message is for the sole use of the intended recipient(s) and may
contain proprietary and confidential information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all copies
of the original message. Thank you