From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Peter Galbavy <peter(dot)galbavy(at)knowtion(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PITR Phase 2 - Design Planning |
Date: | 2004-04-28 06:30:04 |
Message-ID: | 20040428063004.GA6901@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 27, 2004 at 23:02:42 +0000,
Peter Galbavy <peter(dot)galbavy(at)knowtion(dot)net> 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 ?
The context of my suggestion was for recovering up until a transaction which
messed things up was committed. I did not want the problem transaction to
be committed. If the problem transaction ran for a long time, there might
be other transactions that I want to keep, if possible, that committed
after the problem transaction started and before it ended.
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2004-04-28 06:46:09 | Re: bitwise and/or aggregate functions? |
Previous Message | Neil Conway | 2004-04-28 06:08:00 | Re: pgsql-server/src backend/utils/adt/acl.c inclu ... |