On Sun, Oct 4, 2009 at 10:28 PM, Fujii Masao masao.fu...@gmail.com wrote:
I think that xlogdump (http://xlogviewer.projects.postgresql.org/) is
the first step to address that TODO item. Though I'm not sure if the
xlogdump project is still active.
I believe it has been dead for quite awhile
shakahsha...@gmail.com wrote:
Can anyone elaborate (or point me to some additional info) on the 8.5
TODO item in the Point-In-Time Recover (PITR) section (1.4):
Create dump tool for write-ahead logs for use in determining
transaction id for point-in-time recovery
This is useful for
Hi,
On Tue, Oct 6, 2009 at 7:47 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
That TODO item is a lot less important after we have Hot Standby. It
contains functions that allow you to pause and continue WAL replay, and
step through the WAL one transaction at a time.
I
Fujii Masao escreveu:
On Tue, Oct 6, 2009 at 7:47 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
That TODO item is a lot less important after we have Hot Standby. It
contains functions that allow you to pause and continue WAL replay, and
step through the WAL one transaction
Hi,
On Sat, Oct 3, 2009 at 7:30 AM, shakahsha...@gmail.com
shakahsha...@gmail.com wrote:
Can anyone elaborate (or point me to some additional info) on the 8.5
TODO item in the Point-In-Time Recover (PITR) section (1.4):
Create dump tool for write-ahead logs for use in determining
transaction
Can anyone elaborate (or point me to some additional info) on the 8.5
TODO item in the Point-In-Time Recover (PITR) section (1.4):
Create dump tool for write-ahead logs for use in determining
transaction id for point-in-time recovery
This is useful for checking PITR recovery.
I poked
