Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id eBU2MIL61144 for ; Fri, 29 Dec 2000 21:22:18 -0500 (EST) (envelope-from pgsql-docs-owner@postgresql.org) Received: from kechara.flame.org (kechara.flame.org [204.152.184.79]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id eBRG9CL25774 for ; Wed, 27 Dec 2000 11:09:12 -0500 (EST) (envelope-from explorer@flame.org) Received: (qmail 14712 invoked by uid 173); 27 Dec 2000 16:09:27 -0000 To: pgsql-docs@postgresql.org Subject: Rather incorrect text in admin guide From: Michael Graff Date: 27 Dec 2000 08:09:27 -0800 Message-ID: Lines: 22 X-Mailer: Gnus v5.7/Emacs 20.7 X-Archive-Number: 200012/75 X-Sequence-Number: 122 In the admin guide, under the section "Large Databases" is the following paragraph: Since Postgres allows tables larger than the maximum file size on your system, it can be problematic to dump the table to a file, since the resulting file will likely be larger than the maximum size allowed by your system. As pg_dump writes to the standard output, you can just use standard *nix tools to work around this possible problem. This is a generalization of, most likely, a failing in linux. NetBSD (which I use) will allow file sizes up to 2^64 -- I don't think anyone has generated a postgresql database that large yet. You might want to qualify that with "Operating systems which support 64-bit file sizes (such as NetBSD) will have no problem with large databases" or "some operating systems are limited to 2-gigabyte files (such as linux)" --Michael