Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> I think we should be setting the initial epoch to something other than
> zero. That way, some quick testing would have revealed this problem
> immediately.
Yeah, having initdb start the epoch at 1 doesn't seem unreasonable.
regards, tom lane