Обсуждение: jumpstart - pgsql.v824

Hi Everyone,

Is there any way to trick an instance into starting when you just have base, global, pg_clog, pg_mulitxact, pg_subtrans, pg_tblspc, & pg_twophase, but no pg_xlog?

 We weren't backing up the pg_xlog, because we didn't think we needed it, but the backup_label seems to need it.  Even if we take the backup_label file out, and try to start postgres, it doesn't start.

I'm going to start experimenting and testing to see if I can trick it to starting, but if anyone has any insight that would help.  We noticed this on a test restore, so it wasn't a major problem, now we are backing up the pg_xlog files as well.

~DjK

---

Windows Live Hotmail and Microsoft Office Outlook – together at last. Get it now!

Please reread the instructions on pitr and then create an empty pg_xlog directory it can then be filled using what ever you have set "restore_command" to.
I guess thats what you want to achieve?

Peter.

dx k9 <bitsandbytes88@hotmail.com> writes:
> Is there any way to trick an instance into starting when you just have base, global, pg_clog, pg_mulitxact,
pg_subtrans,pg_tblspc, & pg_twophase, but no pg_xlog? 

pg_resetxlog would probably be enough to get it to start, but the odds
of having a non-corrupt database afterwards don't seem very good.

>  We weren't backing up the pg_xlog, because we didn't think we needed it, but the backup_label seems to need it.
Evenif we take the backup_label file out, and try to start postgres, it doesn't start. 

Have you read the manual's chapter on backup/restore?  There are several
documented ways to do things successfully, but inventing your own is not
likely to work.

            regards, tom lane