Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dyNIO-0000oB-I5 for pgsql-committers@arkaria.postgresql.org; Sat, 30 Sep 2017 19:19:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dyNIN-0002JQ-TK for pgsql-committers@arkaria.postgresql.org; Sat, 30 Sep 2017 19:19:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dyNI8-0001sj-Cr for pgsql-committers@postgresql.org; Sat, 30 Sep 2017 19:19:12 +0000 Received: from mail-yw0-x230.google.com ([2607:f8b0:4002:c05::230]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dyNI4-0006eP-Iy for pgsql-committers@postgresql.org; Sat, 30 Sep 2017 19:19:11 +0000 Received: by mail-yw0-x230.google.com with SMTP id i7so1368163ywa.4 for ; Sat, 30 Sep 2017 12:19:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=7p4haGZ7WjZACXUenwxbfVSGmtlU/UsihNx0RB8plA0=; b=GujFC4YEQVVWWOvL/h65cvnikKKcE1FJtAVqYuetdPg4wQKYjnYzcwsgM/Bvvy/n7N oHq6rx5bwtt0f5mli7CjdYJiEjPLQbgtuURlqqah5k0VIyGSkJKE54ddHydcL5XbmG3W qokh8Iux6CQr8MZcHdyzahy2wLW5OdSHW36pgpY7Xj8SE0Ski6syFa9cJAyVpcel9kb8 LJm7dywpCxP6INC1yh+zXuFb1jc0h5qcYAjjlNtmoXyjcZ3UXmJABkPGezDZ25VL08+8 h4a8vPDfMBQwpb/O9kmhAGNtCutTYNyoQssn2Va586wf/Uwdk4mKhEXga1qtHuQR4UjL XKnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=7p4haGZ7WjZACXUenwxbfVSGmtlU/UsihNx0RB8plA0=; b=qDFBjXFOCOcIVTIur6FbaU2mTc5ptEV2IXpI5i3Zou9is0T5R5t9935MGhWx+xfyc6 qmEh9K0kkNapJU4tyGKWO0Aeb+j9ChLxD/D2RwxjXjEElN5b0P7J0qlAUir3gT9ROlUT SiZKRhYAXnijvtbUfDnz9MOCKV8shHt6oy/Wwu/IxIG5VF/rbqwwVzbE1z9Ww0e1Uqix vquyl7I1dKs/I07VQopWqQoYmsSW17pfzEx4IkCP4b8y967IBNdkFqM7G/vWvdum7T3j axOKEoCfW0n/9N4peWzDzrH/SgeBo5kcPMbS5tcIRMgoakDOR6VKTnM7kSK+nakY90UV tlhQ== X-Gm-Message-State: AHPjjUgTAEKnhWgiLNCogffYxLF51J5HxAM04UbgYf6jA15gs7iAl1sJ 9tVYAZVn76llWCLVSgamEd0r/dYxU0fXeFPPoM7Od4H18wrlYYijjZE/CIvzCe8NudNyGyHjd3f by5oDgV6btvDGpE5jfT1bxewT44aV+STChMhV0lfKQUDa9PsQ80w8l94q4B9LtprD2t/hb3rs6w muqAYFC42KHvDiLCOG X-Google-Smtp-Source: AOwi7QBK6gJJCt6gZM+UCR42NfFJOz/KFfgEb/ADcfsCJQl1Re+BU+iSU0TcCXQPjKFrLIHseKailw== X-Received: by 10.37.89.86 with SMTP id n83mr8993249ybb.472.1506799146525; Sat, 30 Sep 2017 12:19:06 -0700 (PDT) Received: from [192.168.10.146] ([98.122.175.38]) by smtp.gmail.com with ESMTPSA id b201sm2866659ywe.20.2017.09.30.12.19.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 30 Sep 2017 12:19:06 -0700 (PDT) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: pgsql: Support arrays over domains. To: Tom Lane , pgsql-committers@postgresql.org References: Message-ID: <678e49f8-e32a-9b96-8e3f-a8c63d2f0e18@2ndQuadrant.com> Date: Sat, 30 Sep 2017 15:19:05 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-MW List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-committers Precedence: bulk Sender: pgsql-committers-owner@postgresql.org On 09/30/2017 01:41 PM, Tom Lane wrote: > Support arrays over domains. We seem to have caused a problem with pg_upgrade :-( The failing log file is: command: "/home/bf/bfr/root/upgrade/HEAD/inst/bin/pg_restore" --host /home/bf/bfr/root/upgrade/HEAD/inst --port 5648 --username buildfarm --exit-on-error --verbose --dbname 'dbname=contrib_regression_hstore' "pg_upgrade_dump_51236.custom" >> "pg_upgrade_dump_51236.log" 2>&1 pg_restore: connecting to database for restore pg_restore: creating pg_largeobject "pg_largeobject" pg_restore: creating pg_largeobject_metadata "pg_largeobject_metadata" pg_restore: creating SCHEMA "public" pg_restore: creating COMMENT "SCHEMA "public"" pg_restore: creating EXTENSION "hstore" pg_restore: creating COMMENT "EXTENSION "hstore"" pg_restore: creating SHELL TYPE "public.ghstore" pg_restore: creating FUNCTION "public.ghstore_in("cstring")" pg_restore: creating FUNCTION "public.ghstore_out("ghstore")" pg_restore: creating TYPE "public.ghstore" pg_restore: creating DOMAIN "public.hstestdom1" pg_restore: [archiver (db)] Error while PROCESSING TOC: pg_restore: [archiver (db)] Error from TOC entry 579; 1247 51354 DOMAIN hstestdom1 buildfarm pg_restore: [archiver (db)] could not execute query: ERROR:  pg_type array OID value not set when in binary upgrade mode     Command was: -- For binary upgrade, must preserve pg_type oid SELECT pg_catalog.binary_upgrade_set_next_pg_type_oid('51354'::pg_catalog.oid); CREATE DOMAIN "hstestdom1" AS integer NOT NULL DEFAULT 0; Here we're upgrading from 9.2 to HEAD. Of course, there isn't an array oid for the domain in 9.2. 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