From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
Cc: Kirby Bohling (TRSi) <kbohling@oasis.novia.net>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: cursor interface to libpq
Date: Fri, 22 Sep 2000 12:31:57 -0400
Message-ID: <29420.969640317@sss.pgh.pa.us> (raw)
In-Reply-To: <39C8E45C.AE72C336@alumni.caltech.edu>
References: <Pine.GSO.4.21.0009201026100.10741-100000@oasis.novia.net>
<39C8E45C.AE72C336@alumni.caltech.edu>
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> afaik this should all work. You can run pg_dump and pipe the output to a
> tape drive or to gzip. You *know* that a real backup will take something
> like the size of the database (maybe a factor of two or so less) since
> the data has to go somewhere.
pg_dump in default mode (ie, dump data as COPY commands) doesn't have a
problem with huge tables because the COPY data is just dumped out in a
streaming fashion.
If you insist on using the "dump data as insert commands" option then
huge tables cause a memory problem in pg_dump, but on the other hand you
are going to get pretty tired of waiting for such a script to reload,
too. I recommend just using the default behavior ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, lockhart@alumni.caltech.edu, kbohling@oasis.novia.net
Subject: Re: cursor interface to libpq
In-Reply-To: <29420.969640317@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox