Skip site navigation (1) Skip section navigation (2)

AW: AW: Big 7.1 open items

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Don Baccus'" <dhogaza(at)pacifier(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: AW: AW: Big 7.1 open items
Date: 2000-06-15 14:27:39
Message-ID: 219F68D65015D011A8E000006F8590C605BA5970@sdexcsrv1.f000.d0188.sd.spardat.at (view raw or flat)
Thread:
Lists: pgsql-hackers
> >> In reality, very few people are going to be interested in restoring
> >> a table in a way that breaks referential integrity and other 
> >> normal assumptions about what exists in the database. 
> >
> >This is not true. In my DBA history it would have saved me manweeks
> >of work if an easy and efficient restore of one single table 
> from backup 
> >would have been available in Informix and Oracle.
> >We allways had to restore most of the whole system to 
> another machine only
> >to get back at some table info that would then be manually re-added
> >to the production system. 
> 
> I'm missing something, I guess.  You would do a createdb, do 
> a filesystem
> copy of pg_log and one file into it, and then read data from the table
>  without having to restore the other tables in the database?

No if you want to restore to a separate postgres instance you need to 
restore all pg system tables as well.
What I meant is create a new table in your production server and replace 
the new 0 byte file with your backup file (rename it accordingly).

Andreas

pgsql-hackers by date

Next:From: Thomas LockhartDate: 2000-06-15 14:29:36
Subject: Re: [HACKERS] info on unixODBC/Postgres driver port to IRIX 6.5.7 64bit
Previous:From: Bruce MomjianDate: 2000-06-15 14:16:54
Subject: Re: [HACKERS] info on unixODBC/Postgres driver port to IRIX 6.5.7 64bit

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group