Tom Lane wrote:
> Bruce Momjian <
bruce@...> writes:
> > Agreed. I realize why we are not zeroing those bytes (for performance),
> > but can't we have the archiver zero those bytes before calling the
> > 'archive_command'?
>
> The archiver doesn't know any more about where the end-of-data is than
> the archive_command does. Moreover, the archiver doesn't know whether
> the archive_command cares. I think the separate module is a fine
> solution.
>
> It should also be pointed out that the whole thing becomes uninteresting
> if we get real-time log shipping implemented. So I see absolutely no
> point in spending time integrating pg_clearxlogtail now.
People doing PITR are still going to be saving these files, and for a
long time, so I think this is still something we should try to address.
Added to TODO:
o Reduce PITR WAL file size by removing full page writes and
by removing trailing bytes to improve compression
--
Bruce Momjian <
bruce@...>
http://momjian.us EnterpriseDB
http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-hackers mailing list (
pgsql-hackers@...)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
