[GENERAL] 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

Re: [GENERAL] [ADMIN] How to set the global OID counter? COPY WITH OIDS does

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 [EMAIL PROTECTED] writes:

Re: [GENERAL] [ADMIN] How to set the global OID counter? COPY WITH OIDS does

True. Dirk Tom Lane wrote: =?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= [EMAIL PROTECTED] 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

[GENERAL] dump/restore needed when switching from 32bit to 64bit processor architecture?

Hi, when have a 8.0.3 database running on a XEON machine. We want to replace it with an Opteron where postgresql is to be compiled with 64bit. Do we need a dump/restore or can we just start the db with the new compilation? Regards, Dirk ---(end of

Re: [GENERAL] [ADMIN] dump/restore needed when switching from 32bit to 64bit

Thanks Tom, we now stay with 32bit to allow backward compatibilty with XEON which is needed as a fail-over system. The question is which gcc cflags are best used with XEON and Opteron to achieve fail-over compatibility. This is what we used for postgresql 8.0.3: XEON, RHEL 3.0 AS: CFLAGS