RE: duplicate OID issue when using pg_upgrade to move from 9.3 to 9.5

From: Duarte Carreira <DCarreira(at)edia(dot)pt>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: RE: duplicate OID issue when using pg_upgrade to move from 9.3 to 9.5
Date: 2019-01-25 15:00:51
Message-ID: AM0PR07MB566796BB81AA1B87A25A90BAA09B0@AM0PR07MB5667.eurprd07.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sure, I'll be sending you the dump shortly off-list.

Duarte

-----Mensagem original-----
De: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Enviada: 25 de janeiro de 2019 14:28
Para: Duarte Carreira <DCarreira(at)edia(dot)pt>
Cc: pgsql-general(at)postgresql(dot)org
Assunto: Re: duplicate OID issue when using pg_upgrade to move from 9.3 to 9.5

Duarte Carreira <DCarreira(at)edia(dot)pt> writes:
> Tom, just did a pg_dump -s from 9.3 and there are no warnings in the output file. It goes smoothly and fast (few seconds). Database is around 50GB, schema 9MB. Has postgis and a few more extensions - ogr_fdw (from postigs), file_fdw, postgres_fdw, table_func.

Hmph. Would you be willing to send me a schema-only dump (off-list!) of the problematic database? The best format would be an "-Fc -s"
pg_dump output, because that would show what pg_dump thinks the dependencies are. Be sure you make it with the newer pg_dump.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Duarte Carreira 2019-01-25 15:16:57 RE: duplicate OID issue when using pg_upgrade to move from 9.3 to 9.5
Previous Message Tom Lane 2019-01-25 14:27:41 Re: duplicate OID issue when using pg_upgrade to move from 9.3 to 9.5