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

At 10:49 3/07/00 +0200, Zeugswetter Andreas SB wrote:
>> 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.

OK: I know nothing about this, but I'd be interested to learn.

The reason I mentioned the WAL is that I think that any more advanced
backup strategy needs to be integrated into the journaling system (ie. the
WAL). Ideally, we should be able to snapshot a consistent view of raw data
and apply a copy of the journal to this snapshot. In other systems I use
(Dec/Rdb), this is done via a page-based backup (I think) and an
after-image journal (both of which I *think* are at a lower level than
tables & rows - more like pages & slots.

As a result, I had planned to wait and see what the WAL did for backup
strategies...

But, in the mean time, if you think a binary pg_dump is possible (an
relatively easy), I'd be interested to try to integrate it...


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.C.N. 008 659 498)             |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/