| From: | Alan Hodgson <ahodgson(at)simkin(dot)ca> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: : PostgreSQL Online Backup |
| Date: | 2011-10-04 17:57:48 |
| Message-ID: | 201110041057.48406.ahodgson@simkin.ca |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > rsync works fine. Why exactly can't the recovery find the backed up copy
> > of 000000010000053900000076? Please post your archive_command settings,
> > the contents of any script(s) called by that, and the recovery.conf file
> > you're using that's having problems, as well as the complete process you
> > followed to
> > initiate recovery. I strongly suspect you're missing part of the process
> > of actually saving the WAL files needed for recovery.
> The recovery is unable to find the WAL archive because, it was generated on
> 26th September.
>
> Whereas the backup is as taken on Oct 2nd, 2011. We deleted all the files.
>
> I do not have that WAL archive copy.
>
> The problem area -
>
> I found that a pg_clog file dated 26th Sep, 2011 is not synced (its not
> 256K).
>
I'm going to need the rest of what I asked for to offer any further suggestions
- especially the full and exact steps you took to initiate recovery and the
contents of recovery.conf. Also, please don't top-post.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J.V. | 2011-10-04 17:59:44 | how to disable all pkey/fkey constraints globally |
| Previous Message | Bob Hatfield | 2011-10-04 17:27:35 | Replication/WAL shipping. db errors on slave after stop/start master |