I've seen things like this happen before. Usually something like a buggy hand-rolled upsert procedure (with improper handling of duplicate violation) is involved. That can burn through transaction IDs very quickly, without a true spike in writes.
-
-
^^
@the_hydrobiont good additions to your collection of Postgres horror stories -
many of them are already there;)
End of conversation
New conversation -
-
-
I've seem people do that but they have complained mostly about vacuum locking things than wal volume. But yeah....
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.