Received: from me.tm.ee (adsl895.estpak.ee [213.168.23.133]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBUC8XL83306 for ; Sat, 30 Dec 2000 07:08:34 -0500 (EST) (envelope-from hannu@tm.ee) Received: from tm.ee (IDENT:hannu@localhost.localdomain [127.0.0.1]) by me.tm.ee (8.9.3/8.9.3) with ESMTP id OAA00921; Sat, 30 Dec 2000 14:05:24 +0200 Message-ID: <3A4DCF84.10CF14E9@tm.ee> Date: Sat, 30 Dec 2000 14:05:24 +0200 From: Hannu Krosing X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.17 i686) X-Accept-Language: en MIME-Version: 1.0 To: Michael Graff CC: pgsql-docs@postgresql.org Subject: Re: Rather incorrect text in admin guide References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200012/78 X-Sequence-Number: 125 Michael Graff wrote: > > 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)" Or more correctly "(such as some versions of linux)" --------- Hannu