From: msteben@autorevenue.com
To: pgsql-admin@postgresql.org
Subject: Re: another PITR recovery question
Date: Thu, 5 Mar 2009 16:46:02 -0500 (EST)
Message-ID: <60032.10.10.6.20.1236289562.squirrel@mail.autorevenue.com> (raw)
In-Reply-To: <41416.10.10.6.20.1236287704.squirrel@mail.autorevenue.com>
References: <41416.10.10.6.20.1236287704.squirrel@mail.autorevenue.com>
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
>
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: msteben@autorevenue.com
Subject: Re: another PITR recovery question
In-Reply-To: <60032.10.10.6.20.1236289562.squirrel@mail.autorevenue.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox