pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-committers@postgresql.org
Subject: Re: pgsql: Support arrays over domains.
Date: Sat, 30 Sep 2017 15:37:20 -0400
Message-ID: <664a27a2-a186-addc-5102-d52109496340@2ndQuadrant.com> (raw)
In-Reply-To: <24123.1506799963@sss.pgh.pa.us>
References: <E1dyLlE-0002gT-H5@gemulon.postgresql.org>
	<678e49f8-e32a-9b96-8e3f-a8c63d2f0e18@2ndQuadrant.com>
	<24123.1506799963@sss.pgh.pa.us>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-committers>



On 09/30/2017 03:32 PM, Tom Lane wrote:
> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>> We seem to have caused a problem with pg_upgrade :-(
>>     pg_restore: [archiver (db)] could not execute query: ERROR:  pg_type
>>     array OID value not set when in binary upgrade mode
>> Here we're upgrading from 9.2 to HEAD. Of course, there isn't an array
>> oid for the domain in 9.2.
> Hmm.  That's pretty annoying.  We could certainly go ahead and assign
> some unused type OID to the new array type, but the receiving backend
> can't really do that, since it doesn't know which type OIDs will be
> assigned later in the dump file.
>
> Maybe we could put the burden on pg_upgrade (pg_dump --binary-upgrade)
> to select an OID that's not in use in the source database.
>
> 			


Yes, I think we'll have to do something like that.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers



view thread (4+ messages)

Message-ID: <664a27a2-a186-addc-5102-d52109496340@2ndQuadrant.com>
Permalink:  ../664a27a2-a186-addc-5102-d52109496340@2ndQuadrant.com/
Also on:    postgresql.org/message-id/664a27a2-a186-addc-5102-d52109496340@2ndQuadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: andrew.dunstan@2ndquadrant.com, tgl@sss.pgh.pa.us
  Subject: Re: pgsql: Support arrays over domains.
  In-Reply-To: <664a27a2-a186-addc-5102-d52109496340@2ndQuadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox