From: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Big 7.4 items |
Date: | 2002-12-16 14:20:09 |
Message-ID: | 200212161950.09083.shridhar_daithankar@persistent.co.in |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Monday 16 December 2002 07:43 pm, you wrote:
> Consider that on the slave which is now the active server (master dead),
> it's possible that the slave's PITR's will be recycled before the master
> can come back up. As such, unless there is a, an archival process for
> PITR or b, a method of streaming PITR's off for archival, the odds of
> using PITR to recover the master (resync if you will) seem greatly
> reduced as you will be unable to replay PITR on the master for
> synchronization.
I agree. Since we are talking about features in future release, I think it
should be added to TODO if not already there.
I don't know about WAL numbering but AFAIU, it increments and old files are
removed once there are enough WAL files as specified in posgresql.conf. IIRC
there are some perl based replication project exist already which use this
feature.
Shridhar
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2002-12-16 14:37:12 | Re: Creating a zero-column table |
Previous Message | Reinoud van Leeuwen | 2002-12-16 14:18:11 | how to make a trigger deferrable |