| From: | Peter Childs <blue(dot)dragon(at)blueyonder(dot)co(dot)uk> |
|---|---|
| To: | |
| Cc: | PgSQL General ML <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Type of application that use PostgreSQL |
| Date: | 2003-10-03 11:13:29 |
| Message-ID: | Pine.LNX.4.44.0310031208550.19189-100000@RedDragon.Childs |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 3 Oct 2003, Ron Johnson wrote:
> On Fri, 2003-10-03 at 04:26, Shridhar Daithankar wrote:
> > Peter Childs wrote:
> [snip]
> > Postgresql do have update logs in form of WAL. However it can not do PITR with
> > log archiving if a node in cluster goes down for extended period. WAL does not
> > handle these situations in current design. Precisely, PITR is the feature that
> > implements this functonality.
No it does not. WAL is Down-Date Logs not update logs. WAL will
enable you to rewind to the beginning of all currently running
transactions after a crash. Ie roll-back not roll-forward.
>
> For those not in the know, PITR is Point In Time Recovery.
>
> And yes, that capability has been around for 20+ years on mainframes
> and minicomputers, but they were/a`re funded a lot higher than the
> PostgreSQL volunteers are!
>
>
It was planned for 7.4 so when is it going to happern now it has
missed 7.4?
Peter Childs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcelo Soares | 2003-10-03 11:16:14 | Discussion about inheritance |
| Previous Message | cad0022 | 2003-10-03 11:09:31 | How to avoid users from viewing functions code |