Just so you know I'm very thankful for your hard work and I'm sure many of
us are. I have been waiting for this kind of functionally in Postgresql!
|---------+---------------------------------->
| | Heikki Linnakangas |
| | <hlinnaka@iki.fi> |
| | Sent by: |
| | pgsql-hackers-owner@pos|
| | tgresql.org |
| | |
| | |
| | 04/23/2004 12:56 PM |
| | |
|---------+---------------------------------->
>--------------------------------------------------------------------------------------------------------||
| | To:
pgsql-hackers@postgresql.org | | cc:
| | Subject: Re: [HACKERS] PITR, nested
transactions,tablespaces, 2-phase commit: Status |
>--------------------------------------------------------------------------------------------------------|
On Sat, 17 Apr 2004, Bruce Momjian wrote:
> Would folks report on the current status of these projects:
>
> o nested transactions (Alvaro Herrera)
> o tablespaces (Gavin Sherry)
> o PITR (Simon Riggs)
> o 2-phase commit (Heikki Linnakangas)
I've been very busy with at work, and haven't had much time to work on the
2-phase commit patch.
I'm keeping a close eye on Alvaro's nested transactions stuff, because it
touches the same areas as 2-phase commits.
One day, while reading postgresql code, I realized that my two-phase
code doesn't do the right thing with snapshots. GetSnapshotData scans
through all running backends, and collects the xids of all running
transactions. I suppose all pre-committed transactions should go to the
snapshot too.
So there's still some work to be done, but I'm still hoping to finish it
in time for 7.5.
- Heikki
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to
majordomo@postgresql.orgso that your message can get through to the mailing list cleanly
*************************************************************************
PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may
containproprietary, confidential and/or privileged information. If you are not the intended recipient, any use,
copying,disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient,
pleasenotify the sender immediately by return e-mail, delete this communication and destroy all copies.
*************************************************************************