From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Peter Childs *EXTERN*" <peterachilds(at)gmail(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: "Resurrected" data files - problem? |
Date: | 2007-11-08 15:47:43 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C287FF50@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Peter Childs wrote:
>> We use a tape backup software that does "incremental backups"
[...]
>> So if we perform our database backups with incremental
>> backups as described above, we could end up with additional
>> files after the restore, because PostgreSQL files can get
>> deleted (e.g. during DROP TABLE or TRUNCATE TABLE).
>>
>> My question is:
>>
>> Could such "resurrected" files (data files, files in
>> pg_xlog, pg_clog or elsewhere) cause a problem for the database
>> (other than the obvious one that there may be unnecessary files
>> about that consume disk space)?
>
> This will not work at all.
Can you give me a good reason why?
> Try re-reading the instructions on backup in the manual.
I know them well. That is why I ask if this questionable procedure
could lead to damage.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-08 15:50:39 | Re: why there is no interval / interval operator? |
Previous Message | Tom Lane | 2007-11-08 15:42:56 | Re: Strange variable behaviour when using it in limit clause in plpgsql stored procedure |