What else is needed for PITR? - Mailing list pgsql-hackers

From Simon Riggs
Subject What else is needed for PITR?
Date
Msg-id NOEFLCFHBPDAFHEIPGBOOELJCCAA.simon@2ndquadrant.com
Whole thread Raw
In response to 7.3.7 packaged ...  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
Could I ask the general question:

"What else is needed for PITR?"

- What isn't clear about how PITR works? what it is or what its good for?
- What additional features are required?
- What additional tools are required to make it useful?
- What additional documentation do we want? (Assuming you've read what's
there)

I want to get the list out now, so we can see review what the priorities
are.

I'm particularly interested in everybody listening that might not feel they
could normally contribute to the discussion, though of course, all comments
are welcome.

Many of these may not be appropriate for 8.0, but we can add these to the
TODO list for 8.1.

Best regards, Simon Riggs


pgsql-hackers by date:

Previous
From: Thomas Hallgren
Date:
Subject: Re: initdb failure on win32
Next
From: "Simon Riggs"
Date:
Subject: Re: Does psql use nested transactions?