Skip site navigation (1) Skip section navigation (2)

Re: > 16TB worth of data question

From: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
To: postgres list <pgsql-general(at)postgresql(dot)org>
Subject: Re: > 16TB worth of data question
Date: 2003-04-29 22:57:02
Message-ID: 1051657022.17628.44.camel@haggis (view raw or flat)
Thread:
Lists: pgsql-general
On Tue, 2003-04-29 at 16:05, Jim C. Nasby wrote:
> 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.

Something like:
# pg_dump -f /dev/sg0 -f /dev/sg1 -f /dev/sg2 -f /dev/sg3 <dbname> 
  OR
# pg_dump -f \(/dev/sg0,/dev/sg1,/dev/sg2,/dev/sg3\) <dbname>

Then, pg_dump would decide what data to send to each device.

-- 
+-----------------------------------------------------------+
| Ron Johnson, Jr.     Home: ron(dot)l(dot)johnson(at)cox(dot)net          |
| Jefferson, LA  USA   http://members.cox.net/ron.l.johnson |
|                                                           |
| An ad currently being run by the NEA (the US's biggest    |
| public school TEACHERS UNION) asks a teenager if he can   |
| find sodium and *chloride* in the periodic table of the   |
| elements.                                                 |
| And they wonder why people think public schools suck...   |
+-----------------------------------------------------------+


In response to

pgsql-general by date

Next:From: Andrew J. KopciuchDate: 2003-04-29 23:05:15
Subject: tsearch - txtidx input
Previous:From: Tom LaneDate: 2003-04-29 22:52:00
Subject: Re: Simple question about messages

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group