Tom Lane <[EMAIL PROTECTED]> writes: > What's worse, once you have excluded writes you have to rescan the entire > table to be sure you haven't missed anything. So in the scenarios where this > whole thing is actually interesting, ie enormous tables, you're still > talking about a fairly long interval with writes locked out. Maybe not as > long as a complete REINDEX, but long.
I was thinking you would set a flag to disable use of the FSM for inserts/updates while the reindex was running. So you would know where to find the new tuples, at the end of the table after the last tuple you read. -- greg ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
