Howdy, all.
I'm interested in compressing archived WAL segments in an environment
set up for PITR in the interests of reducing both network traffic and
storage requirements. However, pg_standby presently checks file sizes,
requiring that an archive segment be exactly the right size to be
considere
On Thu, Oct 23, 2008 at 1:15 AM, Heikki Linnakangas <
[EMAIL PROTECTED]> wrote:
> Charles Duffy wrote:
>
>> I'm interested in compressing archived WAL segments in an environment
>> set up for PITR in the interests of reducing both network traffic and
>> storag
In the absence of further feedback from 'yall (and in the presence of
some positive results from internal QA), I'm adding the posted patch
as-is to the 2008-11 CommitFest queue. That said, any such additional
feedback would be gratefully appreciated.
--
Sent via pgsql-hackers mailing list (pg
Koichi Suzuki wrote:
As Heikki pointed out, the issue is not to decompress the compressed
WAL, but also how we can keep archive log still compressed after it is
handled by pg_standby.
pg_standby makes a *copy* of the segment from the archive, and need only
ensure that the copy is decompressed;
tionate
difference in sort times, relative to the number of rows in each set.
As for the potential for memory leaks - thinking about it.
Thanks,
Charles Duffy.
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The merge sort is here:
>
http://sourceware.org/cgi-bin/cvsweb.cgi/libc/
