AW: AW: Modified pg_dump & new pg_restore need testing. ..

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Philip Warner'" <pjw(at)rhyme(dot)com(dot)au>, "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: AW: AW: Modified pg_dump & new pg_restore need testing. ..
Date: 2000-07-03 08:49:21
Message-ID: 219F68D65015D011A8E000006F8590C605BA59B2@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> It just occurred to me that I may be missing something...do you mean you
> would prefer to avoid the 'COPY' commands as the backup technique? If so,
I
> think that's best left to somebody else (or me, but not now, and probably
> not until the WAL is implemented).

Yes, that was what I was thinking. I don't see a conflicting area with WAL.
I would see this as an extension to libpq and how it handles binary cursors
across different platforms.

>
> Also, defining your own output format is pretty easy; the new
> code defines
> a top level interface (for pg_dump and pg_restore) and an archiver
> interface (for output file formats), if you really want a
> different format.

Sounds like you are doing a great job :-)

My favorite defaults would probably be -Fc -Z0 as you noted in another
posting.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2000-07-03 08:50:04 Re: AW: AW: Modified pg_dump & new pg_restore need testing...
Previous Message Zeugswetter Andreas SB 2000-07-03 08:39:12 AW: AW: Modified pg_dump & new pg_restore need testing. ..