| From: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
|---|---|
| To: | "Adrian Klaver" <adrian(dot)klaver(at)gmail(dot)com>,"bhanu udaya" <udayabhanu1984(at)hotmail(dot)com> |
| Cc: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>,"Chris Travers" <chris(dot)travers(at)gmail(dot)com>,"Magnus Hagander" <magnus(at)hagander(dot)net>, "François Beausoleil" <francois(at)teksol(dot)info>,pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_Restore |
| Date: | 2013-01-21 21:28:10 |
| Message-ID: | 20130121212810.179540@gmx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver wrote:
> On 01/21/2013 08:46 AM, bhanu udaya wrote:
>> Can we achieve this template or pg_Restore in less than 20
>> minutes time.
> Seems to me this is where Point in Time Recovery(PITR) might be
> helpful.
Maybe, if the source is on a different set of drives, to reduce
contention for storage and head movement. Either way it is down to
just a straight file copy, so it is the speed of your disk system
that is the limiting factor, not anything within PostgreSQL.
The more sure way of speeding it up is to add more spindles to your
drive array and make sure you are using a good RAID controller with
battery-backed cache.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | patrick keshishian | 2013-01-21 21:31:55 | Re: Running update in chunks? |
| Previous Message | Richard Huxton | 2013-01-21 21:23:50 | Re: Running update in chunks? |