| From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
|---|---|
| To: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
| Cc: | postgres list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: > 16TB worth of data question |
| Date: | 2003-04-29 21:05:40 |
| Message-ID: | 20030429160540.P66185@flake.decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Apr 29, 2003 at 01:01:39AM -0500, Ron Johnson wrote:
> But pg doesn't guarantee internal consistency unless you pg_dump
> the database in one command "pg_dump db_name > db_yyyymmdd.dmp".
>
> Thus, no parallelism unless there are multiple databases, but if there's
> only 1 database...
It would probably be useful if you could feed a specific transaction
id/timestamp to pg_dump, so that it will take the snapshot as of that
time. Of course, it'd probably be easiest if you could just tell pg_dump
to use X number of threads or dump devices.
--
Jim C. Nasby (aka Decibel!) jim(at)nasby(dot)net
Member: Triangle Fraternity, Sports Car Club of America
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Tessier | 2003-04-29 21:28:55 | Re: Bad timestamp external representation |
| Previous Message | Jim C. Nasby | 2003-04-29 21:02:28 | Re: Performance problems |