Simon Riggs wrote:
Immediate use cases for me would be
* ability to filter WAL records based on database or relation
This patch isn't enough to allow the catalog lookups. Without the
catalog lookups, you might as well implement that as an external tool,
like pglesslog.
* ability to recover quickly from various types of bug, for example if
new freespace code caused a corruption we would be able to sidestep it
and get the database up again quickly without doing resetxlog and losing
data.
That might be useful. But again, could just as well be implemented as an
external tool like pglesslog.
(the new FSM implementation isn't WAL-logged, so that particular
scenario isn't very plausible)
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
