1. 31 3月, 2010 2 次提交
    • H
      Change the retry-loop in standby mode to also try restoring files from · 2a77355e
      Heikki Linnakangas 提交于
      pg_xlog directory. This is essential for replaying WAL records that
      were streamed from the master, after a standby server restart.
      
      If a corrupt record is seen in a file restored from the archive or
      streamed from the master, log it as a WARNING and keep retrying. If the
      corruption is permanent, and not just a glitch in the whatever copies the
      files to the archive or a network error not caught by CRC checks in TCP
      for example, we will keep retrying and logging the WARNING indefinitely.
      But that's better than shutting down completely, the standby is still
      useful for running read-only queries. In PITR the recovery ends at such a
      corrupt record, which is a bit questionable, but that's the behavior we
      had in previous releases and we don't feel like chaning it now. It does
      make sense for tools like pg_standby.
      2a77355e
    • P
      Message tuning · feb5087a
      Peter Eisentraut 提交于
      feb5087a
  2. 30 3月, 2010 7 次提交
  3. 29 3月, 2010 1 次提交
  4. 28 3月, 2010 1 次提交
    • S
      Derive latestRemovedXid for btree deletes by reading heap pages. The · a760893d
      Simon Riggs 提交于
      WAL record for btree delete contains a list of tids, even when backup
      blocks are present. We follow the tids to their heap tuples, taking
      care to follow LP_REDIRECT tuples. We ignore LP_DEAD tuples on the
      understanding that they will always have xmin/xmax earlier than any
      LP_NORMAL tuples referred to by killed index tuples. Iff all tuples
      are LP_DEAD we return InvalidTransactionId. The heap relfilenode is
      added to the WAL record, requiring API changes to pass down the heap
      Relation. XLOG_PAGE_MAGIC updated.
      a760893d
  5. 26 3月, 2010 2 次提交
  6. 25 3月, 2010 7 次提交
  7. 24 3月, 2010 5 次提交
  8. 23 3月, 2010 5 次提交
  9. 22 3月, 2010 5 次提交
  10. 21 3月, 2010 5 次提交