> The starting a new timeline thought works for xlogs, but not for clogs. > No matter how far you go into the future, there is a small (yet > vanishing) possibility that there is a yet undiscovered committed > transaction in the future. (Because transactions are ordered in the clog > because xids are assigned sequentially at txn start, but not ordered in > the xlog where they are recorded in the order the txns complete).
Won't ExtendCLOG take care of this with ZeroCLOGPage ? Else the same problem would arise at xid wraparound, no ? Andreas ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
