BUG #14983: ERROR: duplicate key value violates unique constraint"oid_tbl_oid_key"

Hi Michael,

Sorry for answering so late. I missed your answer.
We are still trying to figure out what is the root cause of this issue with: AIX XLC -O2 32bit.
I see no issue with AIX XLC -O0 32bit or AIX XLC -O2 64bit or AIX GCC -O2 32bit and Linux/* 64bit. However, I have no
Linux32bit machine available. 

Recently, we have discovered that, in file:  src/include/port/atomics/arch-ppc.h , the way the pg_memory_barrier_impl
isimplemented may be differently implemented on AIX when using GCC or XLC. We have to experiment with a change: #if
defined(__GNUC__)|| defined(__xlc__) . 

We'll experiment with your suggestions.


About the buildfarm, I faced a blocking issue.


Sena will help me about PostgreSQL on AIX.


However, reading PostgreSQL documentation, it seems possible that this behavior appears ... by design.
Read lines begining by:  >>>

https://www.postgresql.org/docs/10/static/sql-createtable.html
  CREATE TABLE  WITH ( storage_parameter [= value] [, ... ] )
  This clause specifies optional storage parameters for a table or index;
         see Storage Parameters for more information.
  - The WITH clause for a table can also include OIDS=TRUE (or just OIDS) to specify that rows of the
        new table should have OIDs (object identifiers) assigned to them, or OIDS=FALSE to specify that
        the rows should not have OIDs.
  - If OIDS=FALSE is specified or implied, the new table does not store OIDs and no OID will be assigned
        for a row inserted into it.
    This is generally considered worthwhile, since it will reduce OID consumption and thereby postpone
>>>        the wraparound of the 32-bit OID counter.
>>>    Once the counter wraps around, OIDs can no longer be assumed to be unique,
     which makes them considerably less useful.



Cordialement,

Tony Reix

ATOS / Bull SAS
ATOS Expert
IBM Coop Architect & Technical Leader
Office : +33 (0) 4 76 29 72 67
1 rue de Provence - 38432 Échirolles - France
www.atos.net