On Mar 28, 2008, at 12:15 AM, nick wrote:
> Thanks for the reply, a****sh.
>
> Sorry, should=92ve been more specific.
>
> By running WAL, I mean reprocessing the WALs up to a certain point=20=20
> of time.
>
> For example:
>
> A backup is made at 0000 hours. Something happens. Restore has to be=20=
=20
> made at 2000.
>
> Since the backup is at 0000, 20 hours=92 worth of transactions will
be=20=
=20
> stored in WAL. To get the data up to the 2000 the WALs have to be=20=20
> reprocessed. I realize the only way for this to work is by data file=20=
=20
> duplication, so this mean the service has to be stopped anyway to=20=20
> allow the files to be restored.
>
> But there may be a requirement to not take the system offline so
I=92m=20=
=20
> looking for a method to do the restore and WAL reprocessing
without=20=20
> stopping then starting the service like described in the manual.
>
> It would be of great help if it=92s possible.
>
> Thanks in advance,
>
> Nick
>
You need to put postgres in recovery mode to restore from WAL logs; at=20=
=20
this time, there isn't any way to have any write or read-only access=20=20
to the service while a restore is in progress. For 20 hours' worth
of=20=20
data, depending on your hardware, you're probably looking at 1-3 hours=20=
=20
of restore time before you're caught up.
I don't believe there's a way to have db offline and others
available=20=20
for usage since that will change the timeline.
HTH,
-salman
--=20
Sent via pgsql-novice mailing list (pgsql-novice@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-novice
|
