We're seeing some odd behaviour from a PostgreSQL group - one running as primary and the other as a hot slave using streaming replication.
When a failover event occurs and we switch to the hot slave as primary sequences in tables jump by 33 - so where the last number allocated in the sequence was 100 prior to failover once adding the next entry the sequence will produce the number 133.