Fujii Masao wrote: > On Mon, Feb 22, 2010 at 9:30 PM, Heikki Linnakangas > <heikki.linnakan...@enterprisedb.com> wrote: >> Thinking about this again, I'm not sure this is a good idea. Using >> curFileTLI makes sense if you're going to call pg_xlogfile_name() and >> would expect it to return the filename of the file containing the WAL >> record being replayed. But in other contexts, it seems strange for >> pg_last_replay_timeline() to return the TLI of the first record in the >> file, rather than the actual record replayed. > > Umm... though I might misunderstand your point, curFileTLI is the TLI > appearing in the name of WAL file.
Yes. > So it's not the TLI of the first record in the file, isn't it? Hmm, or is it the TLI of the last record? Not sure. Anyway, if there's a TLI switch in the current WAL file, curFileTLI doesn't always represent the TLI of the current record. -- 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
