| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Galbavy <peter(dot)galbavy(at)knowtion(dot)net> |
| Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PITR Phase 2 - Design Planning |
| Date: | 2004-04-27 22:38:11 |
| Message-ID: | 1083105491.3018.354.camel@stromboli |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2004-05-28 at 00:02, Peter Galbavy wrote:
> Bruno Wolff III wrote:
> > For long running transactions where you want to recover as much as possible,
> > one might also want to recover up until just before a specific transaction
> > committed (as opposed to started).
>
> If your DB has died and you are recovering it, how do you reestablish a
> session so that a transaction can complete ? Doesn't all client
> connections assume that a transaction has failed if the connection to
> the DB fails ?
>
Reasonable question...
You re-establish connection, but cannot resume the failed transaction.
PostgreSQL already has crash recovery...this is for restore from backup
scenarios.
Best Regards, Simon Riggs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2004-04-27 22:46:34 | Re: [HACKERS] What can we learn from MySQL? |
| Previous Message | Simon Riggs | 2004-04-27 22:35:40 | Re: PITR Phase 2 - Design Planning |