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

AW: Proposal: More flexible backup/restore via pg_dump

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: Proposal: More flexible backup/restore via pg_dump
Date: 2000-06-27 13:52:01
Message-ID: 219F68D65015D011A8E000006F8590C605BA599B@sdexcsrv1.f000.d0188.sd.spardat.at (view raw or flat)
Thread:
Lists: pgsql-hackers
> Maybe; I know BackupExec also does some kind of seek to 
> update the TOC at
> end of a backup (which is what I need to do). Then again, 
> maybe that's just
> a rewind. I don't want to get into custom tape formats...
> 
> Do we have any tape experts out there?

Dont lock yourself in on the tape issue, it is the pipes that 
actually add value to the utility, and those can't rewind, seek
or whatever.

pipes can:
	compress, split output, write to storage managers, stripe output,
.....

I guess we would want two formats, one for pipe, and one for a standard
directory.

Andreas

Responses

pgsql-hackers by date

Next:From: Thomas LockhartDate: 2000-06-27 14:05:11
Subject: Re: Makefile for parser
Previous:From: Thomas LockhartDate: 2000-06-27 13:45:29
Subject: Re: SQL99 functions

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