Re: [FEATURE REQUEST] Streaming Onlinebackup (MaybeOFFTOPIC) - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: [FEATURE REQUEST] Streaming Onlinebackup (MaybeOFFTOPIC)
Date
Msg-id E1539E0ED7043848906A8FF995BDA57902685E09@m0143.s-mxs.net
Whole thread Raw
In response to Re: [FEATURE REQUEST] Streaming Onlinebackup (MaybeOFFTOPIC)  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: [FEATURE REQUEST] Streaming Onlinebackup (MaybeOFFTOPIC)
Re: [FEATURE REQUEST] Streaming Onlinebackup (MaybeOFFTOPIC)
List pgsql-hackers
> > Attached is a modified version to implement both of these.  I also
bailed
> > out if there was surplus input.  I tried an optimization of
allocating a
> > separate buffer for outputting the zeros, to avoid repeated memset
calls.
> > It didn't seem to make a very big difference; do you think it's
worth
> > cluttering the code with that?
>
> Would it work to just ftruncate the file?

We would need to teach recovery to accept a short file if the last
record is a
valid switch log XLOG record. RestoreArchivedFile currently bails out if
the file
size is not XLogSegSize.

We need to make exact checks though, or this would reduce reliability.
(e.g. a short file must have records up to the very end)

The probably useful next step would be to pass the current length to the
archive_command,
so it can write the filled part of the file without the need for a
filter.

Andreas


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [FEATURE REQUEST] Streaming Onlinebackup (MaybeOFFTOPIC)
Next
From: "Anoo Sivadasan Pillai"
Date:
Subject: Change request ...