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 1hJehu-0003Z2-OQ for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Apr 2019 13:46:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hJehr-0000rR-Pp for pgsql-hackers@arkaria.postgresql.org; Thu, 25 Apr 2019 13:46:31 +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 1hJehr-0000rG-DS for pgsql-hackers@lists.postgresql.org; Thu, 25 Apr 2019 13:46:31 +0000 Received: from mail-qt1-x841.google.com ([2607:f8b0:4864:20::841]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hJeho-0003ej-KK for pgsql-hackers@postgresql.org; Thu, 25 Apr 2019 13:46:30 +0000 Received: by mail-qt1-x841.google.com with SMTP id s10so48262qtc.11 for ; Thu, 25 Apr 2019 06:46:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=QYNwW4tsrtiv++0TXZmAt2Dgn+p9ICT3aecLkcie3Sw=; b=1r9/LsE7oZpsqGMC3G3aJHfQCS5vHOUgXG3i8GKt8AmXSUa4xxw2eYHja2OTi6dYth TgBi81oQD4tM41hoUF+fwi78LVZsZmqGFBiUJwp+mQ8jUluEkDt4q/Y+y66rt2isBXBX Ky4PcyzdxfUxCcC6S+8JbZ5vCaLsJcKQuDxIKjpup2D7kr61iwbztdmD9+BwMSbFsO2i T7pwQ87P4VkzrOJAY60aQKRDOO/2PxheUBLo53NEwq11tHnPkaHbjpzR3bo6tFgMfGzU c+vgZq29audl0eDMD/Nq4uyGNsBiEMNVUJaVJcXGrDZkd16nYREiBxCAV3UCzfnxw908 mckQ== 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:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=QYNwW4tsrtiv++0TXZmAt2Dgn+p9ICT3aecLkcie3Sw=; b=YW7iSYI4r2cbTXHYABwet7zZA7rHeaQwNR4JYTP3l20pkuCi0SM/eHi7Ve3CTontb+ 0vvJKljHYICmW8tov5wNi23A2Rog527xLLIRoPKm6Bg5V9XjNWUearVsBApK6jrJvEgl OKAhF3B2E7K1+yISrlD4PcaLdQwwAXoF1tQH7VWd4atCVOjBSK6yukEeg74kuyR0xgCT UZh05BvmZFLLUrAKADcfUSrmuKTz4xGthDSaKjohqGRAtmYUfNZlRdNSX/WumhHoRt5m dyK77nO+kdi5PFK2EYv5uaisiwWB9TaiWxTRSHCz+i7qKmlsgjzu7PR14qjPxyYe4vTT BsYg== X-Gm-Message-State: APjAAAVbFXaNCSdxS8jOcsgHrMiLTESnPVKCh/lXBC2h280FSIAEnsvH Wy13qmedWgAFGllA85rjVCeOpQ== X-Google-Smtp-Source: APXvYqzyWQozSqMVcAVxaIQqW78tKrKlsgHjt3CCcpuqev4V8raHVxJolFOmd9uxIr5BodpQl4xi3w== X-Received: by 2002:ac8:3758:: with SMTP id p24mr17579831qtb.3.1556199986252; Thu, 25 Apr 2019 06:46:26 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.29.3]) by smtp.gmail.com with ESMTPSA id i62sm3886210qkc.78.2019.04.25.06.46.24 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 25 Apr 2019 06:46:25 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 0FADF120872; Thu, 25 Apr 2019 09:46:23 -0400 (-04) Date: Thu, 25 Apr 2019 09:46:23 -0400 From: Alvaro Herrera To: Amit Langote Cc: Tom Lane , Amit Langote , Michael Paquier , jianingy.yang@gmail.com, PostgreSQL mailing lists , Pg Hackers Subject: Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table Message-ID: <20190425134623.GA26586@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <6aa609be-9295-e2a4-f6d4-266e2ca79f56@lab.ntt.co.jp> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Haven't read the patch, but I tried applying it on top of my tablespace fixing patch ... and my first report is that this query in regress fails (three times): select conname, obj_description(oid, 'pg_constraint') from pg_constraint where conname = 'c_chk' order by 1, 2; conname | obj_description ---------+--------------------------------------- + c_chk | alttype_cleanup_idx check constraint c_chk | alttype_cleanup_idx1 check constraint c_chk | alttype_cleanup_idx2 check constraint - c_chk | alttype_cleanup_idx check constraint (3 rows) I think you should use 'ORDER BY 2 COLLATE "C"' to avoid the problem. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services