On Fri, Feb 12, 2010 at 7:15 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> That's actually a bit questionable, always has been even in pg_standby.
> It adds a constant 1 s delay to the recovery each WAL file, which
> effectively rate-limits the WAL recovery to 16MB per second. I think we
> should rather add a warning to the docs, suggesting the copy-then-rename
> method on Windows.
Right. Adding a warning to the docs looks enough.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
In response to
Responses
pgsql-docs by date
| Next: | From: Simon Riggs | Date: 2010-02-12 12:51:20 |
| Subject: Re: Re: [COMMITTERS] pgsql: Make standby server
continuously retry restoring the next WAL |
| Previous: | From: Heikki Linnakangas | Date: 2010-02-12 10:15:31 |
| Subject: Re: Streaming Replication docs |
pgsql-hackers by date
| Next: | From: Tim Bunce | Date: 2010-02-12 10:40:13 |
| Subject: Re: Add on_trusted_init and on_untrusted_init to plperl
UPDATED [PATCH] |
| Previous: | From: Fujii Masao | Date: 2010-02-12 10:15:32 |
| Subject: Re: TCP keepalive support for libpq |