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.
I'm afraid pg_standby cannot handle this solely, may need some support by the pg core. For example, after closing archive log in archive recovery, pg_core can call some backend to re-compress the archive log for later use. I'm not sure if archive_commend argument works in this scene too, but very sceptical not. Any further thoughts? ----------------- Koichi Suzuki 2008/10/25 Charles Duffy <[EMAIL PROTECTED]>: > 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 (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
