Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hJN95-0004wp-P9 for pgsql-hackers@arkaria.postgresql.org; Wed, 24 Apr 2019 19:01:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hJN94-0003NX-IC for pgsql-hackers@arkaria.postgresql.org; Wed, 24 Apr 2019 19:01:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hJN94-0003NQ-3d for pgsql-hackers@lists.postgresql.org; Wed, 24 Apr 2019 19:01:26 +0000 Received: from mail-qt1-x843.google.com ([2607:f8b0:4864:20::843]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hJN91-0003iT-5b for pgsql-hackers@lists.postgresql.org; Wed, 24 Apr 2019 19:01:24 +0000 Received: by mail-qt1-x843.google.com with SMTP id p20so21578413qtc.9 for ; Wed, 24 Apr 2019 12:01:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=syE5nYyiSwcdbvx5tbnVVM5J2o/jOQ97E33mNxrOtNk=; b=YGlX6GgRjN7mwWs1po7xZpNk750mGV9uqOmstUxDQO+bDLkIhqKl1zROs8ho5n8qoW SQF18OHJ7bq5Gm10SeT831cgQOhgizdVGqrf9va8hJJvRyYmJNhj/gWXPZpou+W3Mnp5 gdqa46ARoe6484B5dMofeHuVoVv8SBx/stRHaVnwyc1v+WDpzdgIydwaj3T9vkqNhQX+ MMNSQlXoc8NxfNa8GTMv1gkYdyC7hSRXxqt8Cdro6aGhwgrDiG4571IWXRxxj/WR1ABP CDdNgCid4eiI62XiX7ItJ4mFKHnE5kvCzmIFYkreueKd4V7iaStTCdr6YsJymWNOUY++ DzyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=syE5nYyiSwcdbvx5tbnVVM5J2o/jOQ97E33mNxrOtNk=; b=P8/W41NmFl8LlXcGSGakLOtniTtLndfyuwSCvxHJV84wxsZlFeHSr0FJkOO8oUCoqo QxXqDayXA94h3RV4Hat2SKBD5hO6gDy/mpnR976k9SYIr9q+OIQLvaBx5bQETEU7RLQv cLL1fINtagk8vAdLB9fYem8v3TMEZzqGwPc/FxjLRTOhyODeBMDnS+4OElDW1SkeoRoy lFBx+RWEsiO0lLw7D39ujl10TQtDkFYWalMVGjEGcHuzunJ4n9JtP3+c2822UD54vc0n TkzxTsyVt4glNVeDUcFRCEQOHv2yh+aw9JwoaJ64lh9wyu3clvRhdQsR1clumWmOGUHT 0Ezw== X-Gm-Message-State: APjAAAUIoPFgw4Bf/yDUNP5/MR5ZTwprUPkyV7V7KkHdxG71iTVCRl+J TnAQvl6gj7idJNFfGj3uYEjwn8s7srnL42iyHMNFlrvWq9mWEUSvmHcoryg46BebXU4JtP5qeMI 0tzsPstt2GmpcNWqkn3Y108hloRusJejTysg8FvLnKO3SZ+5AKPZzL7B0vW2P25LX9BhpLE5SpO ppwDqlVkO1Ii9FyA== X-Google-Smtp-Source: APXvYqyb+zXynFAs5ckNUIz/9qt9n0x86TXtsfI+cge9jH0dYoigNIoAZ9AgjcLqRmIbge2m2MRmGQ== X-Received: by 2002:ac8:3498:: with SMTP id w24mr18711926qtb.153.1556132481484; Wed, 24 Apr 2019 12:01:21 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id b24sm9436931qtr.51.2019.04.24.12.01.20 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 24 Apr 2019 12:01:20 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 0615812081F; Wed, 24 Apr 2019 15:01:18 -0400 (-04) Date: Wed, 24 Apr 2019 15:01:18 -0400 From: Alvaro Herrera To: Pg Hackers Subject: Re: pg_dump partitions can lead to inconsistent state after restore Message-ID: <20190424190117.GA3684@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190423185007.GA27954@alvherre.pgsql> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk So, while testing this I noticed that pg_restore fails with deadlocks if you do a parallel restore if the --load-via-partition-root switch was given to pg_dump. Is that a known bug? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services