this is an important enough question that no one who asks it has to provide an answer as to why they're doing it.
i can imagine many situations where this would be useful, not the least of which is reliability testing. and ESPECIALLY since OID's apparently roll over at 2^32. what happens if you have more than 4 billion rows in the database?
that's totally unrelated to setting the oid counter though. come on. give it up! how do you do it?
colin
On 6/9/06, Dirk Lutzebäck < lutzeb@aeccom.com> wrote: This is not a large object. We are seeing rows with duplicate oids because the OID counter is not changed after the dump (exported with --oids) is being loaded.
How does 8.1 prevent to allocate duplicate OIDs?
Regards,
Dirk
Tom Lane wrote:
Alvaro Herrera <alvherre@commandprompt.com> writes:
Dirk Lutzebäck wrote:
how can one set the global OID counter in 8.1.X? We think it would work
in 8.0.X using the COPY WITH OIDS command but this does not work in
8.1.X anymore.
pg_resetxlog -o
(Postmaster stopped of course)
Possibly more to the point: why do you think you need to mess with the
counter? 8.1 is smart enough not to assign conflicting OIDs to large
objects.
regards, tom lane
