From: "Michael Paquier" <michael.paqu...@gmail.com>
As far as I recall, I don't think so. The problem and the way to solve that are clear. The only trick is to be sure that recovery is done just until a consistent point is reached, and to implement that cleanly.May I implement this feature and submit a patch for the next commitfest if I have time?Please feel free. I might as well participate in the review.
I've done with the attached patch. I also confirmed that the problem I raised in the first mail of the below thread was solved with this patch.
[bug fix] PITR corrupts the database cluster http://www.postgresql.org/message-id/F93E42280A9A4A5EB74FC7350C801A20@maumauI'm wondering if I can do this with cleaner and less code. It would be grateful if you could give me any advice.
Description: Binary data
-- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers