AW: AW: Modified pg_dump & new pg_restore need testing. .. - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: AW: Modified pg_dump & new pg_restore need testing. ..
Date
Msg-id 219F68D65015D011A8E000006F8590C605BA59B2@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List 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


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: AW: AW: Modified pg_dump & new pg_restore need testing...
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: AW: AW: Modified pg_dump & new pg_restore need test ing...