On Wed, Dec 23, 2009 at 2:42 AM, Simon Riggs <si...@2ndquadrant.com> wrote: > The backup history file is a slightly bit quirky way of doing things and > was designed when the transfer mechanism was file-based. > > Why don't we just write a new xlog record that contains the information > we need? Copy the contents of the backup history file into the WAL > record, just like we do with prepared transactions. That way it will be > streamed to the standby without any other code being needed for SR, > while we don't need to retest warm standby to check that still works > also.
This means that we can replace a backup history file with the corresponding xlog record. I think that we should simplify the code by making the replacement completely rather than just adding new xlog record. Thought? BTW, in current SR code, the capability to replicate a backup history file has been implemented. But if there is better and simpler idea, I'll adopt it. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
