From: | msteben(at)autorevenue(dot)com |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: another PITR recovery question |
Date: | 2009-03-05 21:46:02 |
Message-ID: | 60032.10.10.6.20.1236289562.squirrel@mail.autorevenue.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
May be helpful to add on some memory information to my question:
shared_buffers - 250MB
work_mem - 75 MB
maintenance_work_mem - 100MB
max_fsm_pages - 1500000
wal_buffers - 96
checkpoint_segments - 32
And some information on the machine (VMWARE)
ipcs -l
------ Shared Memory Limits --------
max number of segments = 4096
max seg size (kbytes) = 4194303
max total shared memory (kbytes) = 1073741824
min seg size (bytes) = 1
This is the only process running on this virtual machine.
Thanks,
Mark
>
> I'm running postgres 8.2.5 and I'm running a PITR restore on a
> remote machine.
> The archived logs are being restored at a rate of about 5 every 3 minutes
> I was reading in compressed logs and uncompressing them as they are being
> restored. I am now reading in uncompressed logs straight into the restore.
>
> The restore rate only improved slightly - to the rate of 6 every 3
> minutes.
>
> Is there something I can do in postgresql.conf or in the shared memory to
> get this to move faster? At this rate my recovery will run for days as
> I'm
> copying WAL logs from my production machine.
>
>
> Thanks
>
>
>
> Mark Steben
>
> Autorevenue
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Liao | 2009-03-06 11:43:50 | multi-threading access problem |
Previous Message | msteben | 2009-03-05 21:15:03 | another PITR recovery question |