From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | "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:08:08 |
Message-ID: | 20071212100808.5d0655dc@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 12 Dec 2007 18:02:39 +0000
Gregory Stark <stark(at)enterprisedb(dot)com> wrote:
> I'm not sure what you guys' expectations are, but if you're restoring
> 5 minutes worth of database traffic in 8 seconds I wouldn't be
> complaining.
I would be. This is a database that is doing nothing but restoring.
Zero concurrency. This thing should be flying.
>
> 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?
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
SELECT 'Training', 'Consulting' FROM vendor WHERE name = 'CMD'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHYCOIATb/zqfZUUQRAlbBAJ0aNmWy8xFKtmaONUmL9LegTfaaywCfSoS3
TRmDPUEhoTJJVSO8REM6YYI=
=bv/t
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-12-12 18:09:35 | Re: very slow query |
Previous Message | Gregory Stark | 2007-12-12 18:02:39 | Re: Slow PITR restore |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Trout | 2007-12-12 18:13:35 | Re: Slow PITR restore |
Previous Message | Gregory Stark | 2007-12-12 18:02:39 | Re: Slow PITR restore |