Alvaro Herrera <alvhe...@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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
