| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | Zeugswetter Andreas ADI SD <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Slow PITR restore |
| Date: | 2007-12-14 15:37:42 |
| Message-ID: | Pine.GSO.4.64.0712141024150.25424@westnet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Fri, 14 Dec 2007, Zeugswetter Andreas ADI SD wrote:
> I don't follow. The problem is not writes but reads. And if the reads
> are random enough no cache controller will help.
The specific example Tom was running was, in his words, "100% disk write
bound". I was commenting on why I thought that was on his system and why
it wasn't representative of the larger problem. You need at least a basic
amount of write caching for this situation before the problem moves to
being read seek bound.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-12-14 16:06:54 | Re: pgsql constraints and temporal tables |
| Previous Message | Stephen Frost | 2007-12-14 14:16:53 | Re: rewrite pl/pgsql functions to c - remote job |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2007-12-14 15:39:14 | Re: [HACKERS] buildenv.pl/buildenv.bat |
| Previous Message | Andrew Dunstan | 2007-12-14 15:30:10 | Re: buildenv.pl/buildenv.bat |