| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_migrator progress |
| Date: | 2009-03-28 17:51:17 |
| Message-ID: | 19715.1238262677@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
would it matter anyway? We fixed the problems with oid collisions
some time ago.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-03-28 18:09:21 | Re: tuplestore API problem |
| Previous Message | Tom Lane | 2009-03-28 17:01:41 | Re: [COMMITTERS] pgsql: Temporarily (I hope) disable flattening of IN/EXISTS sublinks |