Bruce Momjian <br...@momjian.us> writes:
> Tom Lane wrote:
>> But having said that, there isn't any real harm in fixing the OID
>> counter to match what it was. You need to run pg_resetxlog to set the
>> WAL position and XID counter anyway, and it can set the OID counter too.
> FYI, I decided against restoring the oid counter because it might
> collide with an oid assigned during pg_migrator schema creation.
That argument seems pretty empty --- why is it more likely than a
collision happening if you *don't* restore the oid counter? And why
would it matter anyway? We fixed the problems with oid collisions
some time ago.
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
