On Tue, 2006-08-08 at 13:48 -0500, Ron Johnson wrote:
> >> I'm imagining something similar to the following:
> >> mydb=# select pg_start_backup('mybackup');
> >>
> >> $ tar zcf - /path/to/pgdata | mux.script /dev/st0 /dev/st1 /dev/st2
> >> $ tar zcf - /path/to/tablespace1 | mux.script /dev/st3 /dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Davis wrote:
> On Tue, 2006-08-08 at 09:47 -0700, Jeff Davis wrote:
>> I'm imagining something similar to the following:
>> mydb=# select pg_start_backup('mybackup');
>>
>> $ tar zcf - /path/to/pgdata | mux.script /dev/st0 /dev/st1 /dev/st2
>> $ t
On Tue, 2006-08-08 at 09:47 -0700, Jeff Davis wrote:
> I'm imagining something similar to the following:
> mydb=# select pg_start_backup('mybackup');
>
> $ tar zcf - /path/to/pgdata | mux.script /dev/st0 /dev/st1 /dev/st2
> $ tar zcf - /path/to/tablespace1 | mux.script /dev/st3 /dev/st4 /dev/st5
>
On Mon, 2006-08-07 at 21:10 -0500, Ron Johnson wrote:
> > What situation are you worried about here exactly?
>
> Backing up a large database in a limited amount of time.
>
> If the DB is large enough, and the time is short enough, then the
> single-reader pg_dump can not read the data fast enough
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Davis wrote:
> On Mon, 2006-08-07 at 16:57 -0500, Ron Johnson wrote:
>>> Attach X tape drive, put in a bunch of tapes, and just pg_dump > mdt0
>>> and you're backing up. Restore the other way around.
>> Tape RAID? I like that
>>
>> If the di
On Mon, 2006-08-07 at 16:57 -0500, Ron Johnson wrote:
> > Attach X tape drive, put in a bunch of tapes, and just pg_dump > mdt0
> > and you're backing up. Restore the other way around.
>
> Tape RAID? I like that
>
> If the disk system can keep the tape system full, though.
>
What situatio
On Mon, 2006-08-07 at 16:53 -0500, Ron Johnson wrote:
> > It will be difficult to have a consistent dump though. You can't do
> > that with separate transactions. (And you can't have multiple
> > simultaneous readers without separate transactions.)
>
> Absolutely, you're right. All "threads" mu
On Mon, 2006-08-07 at 16:51 -0500, Ron Johnson wrote:
> Python queues and threads would make that very simple. Master
> thread reads from pg_dump pipe, passing X bytes to a queue, and each
> thread performs this loop:
> - read from queue
> - synchronously write to /dev/stN
Right, you can use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Marlowe wrote:
> On Mon, 2006-08-07 at 16:09, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Scott Marlowe wrote:
>>> On Mon, 2006-08-07 at 15:18, Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alvaro Herrera wrote:
> Ron Johnson wrote:
>
>> This is where a multi-threaded pg_tapedump would be more effective,
>> since it would be able to, for example, have 4 threads reading
>> (different parts of) the database and writing to 4 separate tape d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Davis wrote:
> On Mon, 2006-08-07 at 14:51 -0500, Ron Johnson wrote:
>
>> What would be darned useful (but only, I think, with heavy usage of
>> tablespaces) is:
>> $ pg_tapedump /some/database /dev/st0,/dev/st1,/dev/st2,/dev/st3
>
> I must be
On Mon, 2006-08-07 at 16:09, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Scott Marlowe wrote:
> > On Mon, 2006-08-07 at 15:18, Ron Johnson wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >> Scott Marlowe wrote:
> >>> Oh, I see where you were heade
Ron Johnson wrote:
> This is where a multi-threaded pg_tapedump would be more effective,
> since it would be able to, for example, have 4 threads reading
> (different parts of) the database and writing to 4 separate tape drives.
It will be difficult to have a consistent dump though. You can't do
On Mon, 2006-08-07 at 14:51 -0500, Ron Johnson wrote:
> What would be darned useful (but only, I think, with heavy usage of
> tablespaces) is:
> $ pg_tapedump /some/database /dev/st0,/dev/st1,/dev/st2,/dev/st3
I must be missing something. What is stopping you from doing something
along the line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Marlowe wrote:
> On Mon, 2006-08-07 at 15:18, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Scott Marlowe wrote:
>>> Oh, I see where you were headed.
>>>
>>> I've found a bit here and there googling about for multip
On Mon, 2006-08-07 at 15:18, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Scott Marlowe wrote:
> >
> > Oh, I see where you were headed.
> >
> > I've found a bit here and there googling about for multiplex and tar,
> > and found an IO:Multiplex module for perl.
> >
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Marlowe wrote:
> On Mon, 2006-08-07 at 14:51, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Scott Marlowe wrote:
>>> On Mon, 2006-08-07 at 13:51, Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Broersma Jr wrote:
>> Say we have a 7GB database. Is there a way to way to use 2 tape
>> drives... Argh, I guess not, since the Unix pipe mentality presumes
>> that the mode of operation will be:
>> $ pg_dump /some/database | tar cvfz /dev/
On Mon, 2006-08-07 at 14:51, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Scott Marlowe wrote:
> > On Mon, 2006-08-07 at 13:51, Ron Johnson wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA1
> >>
> >> Jeff Davis wrote:
> >>> On Mon, 2006-07-31 at 09:53 -0500
> Say we have a 7GB database. Is there a way to way to use 2 tape
> drives... Argh, I guess not, since the Unix pipe mentality presumes
> that the mode of operation will be:
> $ pg_dump /some/database | tar cvfz /dev/st0/db.tgz
>
> What would be darned useful (but only, I think, with heavy us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Marlowe wrote:
> On Mon, 2006-08-07 at 13:51, Ron Johnson wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Jeff Davis wrote:
>>> On Mon, 2006-07-31 at 09:53 -0500, Ron Johnson wrote:
>
>>> pg_dump just produces output. You could
On Mon, 2006-08-07 at 13:51, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jeff Davis wrote:
> > On Mon, 2006-07-31 at 09:53 -0500, Ron Johnson wrote:
> > pg_dump just produces output. You could pretty easily stripe that output
> > across multiple devices just by using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff Davis wrote:
> On Mon, 2006-07-31 at 09:53 -0500, Ron Johnson wrote:
>
>>> The evasive answer is that you probably don't run regular full pg_dump
>>> on such databases.
>> Hmmm.
>>
>
> You might want to use PITR for incremental backup or mainta
On Mon, 2006-07-31 at 09:53 -0500, Ron Johnson wrote:
> > The evasive answer is that you probably don't run regular full pg_dump
> > on such databases.
>
> Hmmm.
>
You might want to use PITR for incremental backup or maintain a standby
system using Slony-I ( www.slony.info ).
> >> Are there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Eisentraut wrote:
> Ron Johnson wrote:
>> I think I've read that there are multi-hundred GB PostgreSQL
>> databases.
>>
>> Since pg_dump is single-threaded, how long does it take to back up
>> such a database?
>
> The evasive answer is that you
Ron Johnson wrote:
> I think I've read that there are multi-hundred GB PostgreSQL
> databases.
>
> Since pg_dump is single-threaded, how long does it take to back up
> such a database?
The evasive answer is that you probably don't run regular full pg_dump
on such databases.
> Are there any plans
26 matches
Mail list logo
