Re: PG and undo logging - Mailing list pgsql-general

From David G. Johnston
Subject Re: PG and undo logging
Date
Msg-id CAKFQuwZdZhmKhH=du=1Xo2tUgbaukEuf4Zmk47MaT-AGx3k6RQ@mail.gmail.com
Whole thread Raw
In response to Re: PG and undo logging  (Ravi Krishna <sravikrishna3@gmail.com>)
List pgsql-general
On Saturday, May 23, 2015, Ravi Krishna <sravikrishna3@gmail.com> wrote:
undo means that reading the WAL logs and able to rollback a row back
to its original state before the update. Typically it is used to
rollback a long running transaction which got aborted due to a crash.
Here is an example:


Not an expert here but...

It doesn't matter why the newly written data was deemed invalid, MVCC ensures that absent a successful commit all of that data is considered invisible to anything other than the session writing the data.  Eventually vacuum is needed to cleanup the dead data.

One possible implementation is that uncommitted data simply is never written to the data files...only the buffers see the changes until commit when the WAL sees it.  This seems likely but I do not know for sure.

David J.

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3
Next
From: Daniel Begin
Date:
Subject: Re: FW: Constraint exclusion in partitions