| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Michael Graff <explorer(at)flame(dot)org> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Rather incorrect text in admin guide |
| Date: | 2000-12-30 12:05:24 |
| Message-ID: | 3A4DCF84.10CF14E9@tm.ee |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2000-12-30 12:09:32 | Re: Postgres ignoring RTree for geometric operators |
| Previous Message | Tatsuo Ishii | 2000-12-30 03:07:59 | Re: [HACKERS] About PQsetClientEncoding(),"SET NAMES",and "SET CLIENT_ENCODING" |