Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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
We don't transfer any system-level oids so there is no chance of a
collision against system tables.
> would it matter anyway? We fixed the problems with oid collisions
> some time ago.
Oh, we handled that; OK, old code restored.
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ If your life is a hard drive, Christ can be your backup. +
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2009-03-28 19:28:33|
|Subject: Re: [COMMITTERS] pgsql: Temporarily (I hope) disable
flattening of IN/EXISTS sublinks|
|Previous:||From: Bruce Momjian||Date: 2009-03-28 19:17:10|
|Subject: Re: PQinitSSL broken in some use casesf|