| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | samantha mahindrakar <sam(dot)mahindrakar(at)gmail(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Rollback in Postgres |
| Date: | 2008-07-11 18:58:48 |
| Message-ID: | 1215802728.4051.1577.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Fri, 2008-07-11 at 11:21 -0600, Scott Marlowe wrote:
> rollback after commit
Are you sure?
Personally I don't think its viable. If it really does that it will
would also need to rollback all transactions whose changes depend upon
the earlier transaction. It would also need to track transactions that
read data changed by an earlier transaction and then makes changes to
the database. It's got no way to track that without extensive and costly
additional infrastructure, since after transaction commit row locking
information can be cleaned up by read-only transactions accessing those
changed data blocks.
Flashback query allows reading data as it was at a certain point in the
past. We might one day provide that, but undoing individual transactions
isn't ever going to be feasible, without unknowable risk.
Not jumping on you, just think their marketing is ahead of the reality.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-07-11 20:00:25 | Re: Unnecessary repeat condition for a self inner join |
| Previous Message | Steve Crawford | 2008-07-11 18:56:06 | Re: When was my database created |