Received: from spider.pilosoft.com (p55-222.acedsl.com [160.79.55.222]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eB10AmF29967 for ; Thu, 30 Nov 2000 19:10:48 -0500 (EST) (envelope-from alex@pilosoft.com) Received: from localhost (alexmail@localhost) by spider.pilosoft.com (8.9.3/8.9.3) with ESMTP id TAA21190; Thu, 30 Nov 2000 19:12:35 -0500 (EST) Date: Thu, 30 Nov 2000 19:12:35 -0500 (EST) From: Alex Pilosov To: "Mr. Shannon Aldinger" cc: pgsql-general@postgresql.org Subject: Re: Can PostGreSQL handle 100 user database? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200011/1018 X-Sequence-Number: 1164 On Thu, 30 Nov 2000, Mr. Shannon Aldinger wrote: > Linux kernel 2.2.x unpatched has the 2GB file size and 1GB ram limit. > Patched with the lfs package the 2GB file size limit goes away. > The lfs patch needs applied against gnu-libc as well. This alone may not > avoid the 2GB limit, the application must use the lseek64 instead of > lseek, for example. lfs will be included by default in the upcoming 2.4.x That's automatic, if you compile your source with -D_LARGE_FILES (or something like that, don't remember exact names). > kernels. The upcoming 2.4.x kernels also support more ram. I'm fairly > certain ram patches exist for the 2.2.x series. > > I have just one question to ask will postgresql 7.1 include full support > for using lseek64, stat64, etc? Postgres doesn't need to. Just autoconf script needs to have an option --with-large-files argument that would add -D_LARGE_FILES to CFLAGS. -alex