From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Jeff Trout <threshar(at)threshar(dot)is-a-geek(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Slow PITR restore |
Date: | 2007-12-12 18:19:40 |
Message-ID: | 1197483580.4255.1605.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Wed, 2007-12-12 at 10:08 -0800, Joshua D. Drake wrote:
> > Depending on your transaction mix and what percentage of it is
> > read-only select queries you might reasonably expect the restore to
> > take as long as it took to generate t
>
> We archive selects?
No, but that is exactly his point.
Whatever proportion of the workload is selects will *not* have to be
reproduced on the client.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | D. Dante Lorenso | 2007-12-12 18:21:05 | Re: Function to convert from TEXT to BYTEA? |
Previous Message | Scott Marlowe | 2007-12-12 18:18:57 | Re: about the performance of autovacuum and vacuumdb? |
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schiltknecht | 2007-12-12 18:23:49 | Re: VLDB Features |
Previous Message | Jeff Trout | 2007-12-12 18:13:35 | Re: Slow PITR restore |