Tom Lane wrote:
> [EMAIL PROTECTED] writes:
>
>>I'm currently looking at using WAL / PITR backups for a database, and I
>>need to keep the backups as up to date as possible. As such, keeping a
>>copy of the current WAL file, as suggested in the manual, would seem to be
>>a very good idea. I'm s
OK, thanks.
[EMAIL PROTECTED] writes:
> I'm currently looking at using WAL / PITR backups for a database, and I
> need to keep the backups as up to date as possible. As such, keeping a
> copy of the current WAL file, as suggested in the manual, would seem to
be
> a very good idea. I'm
[EMAIL PROTECTED] writes:
> I'm currently looking at using WAL / PITR backups for a database, and I
> need to keep the backups as up to date as possible. As such, keeping a
> copy of the current WAL file, as suggested in the manual, would seem to be
> a very good idea. I'm slightly confused, tho
Hi,
I'm currently looking at using WAL / PITR backups for a database, and I
need to keep the backups as up to date as possible. As such, keeping a
copy of the current WAL file, as suggested in the manual, would seem to be
a very good idea. I'm slightly confused, though, about which file is the
