Обсуждение: How to set the global OID counter? COPY WITH OIDS does not set global OID counter?

Hi,

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.

We have the problem that we made a dump using 'pg_dump -o' in 8.0.X,
created a new database in 8.1.X and read back in but the global OID
counter stayed at 40.000 so OIDs will be allocated again!

Thanks for help,

Dirk

Dirk Lutzebäck wrote:
> Hi,
>
> 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)

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

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

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 

=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb@aeccom.com> writes:
> 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?

If there's a unique index on the OID column then 8.1 will not allocate
duplicate OIDs.  If there's not such a unique index, you had no
guarantee of no-duplicates before 8.1 either.

            regards, tom lane

True.

Dirk

Tom Lane wrote:

Dirk Lutzebäck <lutzeb@aeccom.com> writes: 

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?   

If there's a unique index on the OID column then 8.1 will not allocate
duplicate OIDs.  If there's not such a unique index, you had no
guarantee of no-duplicates before 8.1 either.
		regards, tom lane