From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, apoc9009(at)yahoo(dot)de, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [FEATURE REQUEST] Streaming Onlinebackup (Maybe OFFTOPIC) |
Date: | 2007-09-06 23:23:42 |
Message-ID: | 5803.1189121022@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Thu, 2007-09-06 at 12:08 +0100, Heikki Linnakangas wrote:
>> With file-based log shipping, you can get down to 1 second, by using the
>> archive_timeout setting. It will produce a lot of log files with very
>> little content in them, but they will compress well.
> I tried doing a couple pg_switch_xlog() in quick succession, and the WAL
> files that represent less than a second of actual data don't seem much
> more compressible than the rest.
That's because we do not try to zero out a WAL file when recycling it,
so the part after what's been used is not any more compressible than the
valid part.
pg_switch_xlog is not, and was never intended to be, a solution for a
low-latency log-shipping scheme. The right solution for that is to make
a smarter log-shipping daemon that transmits only part of a WAL segment
at a time. (As Hannu is getting tired of repeating, you can find a
working example in SkyTools.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | korry.douglas | 2007-09-06 23:41:00 | Re: Trouble with the PL/pgSQL debugger and VC++ |
Previous Message | Charlie Savage | 2007-09-06 23:08:20 | Re: Some more msvc++ 8.2.4 build feedback |