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 1iKPsX-0001V0-4V for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Oct 2019 16:40:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iKPsV-00023B-Et for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Oct 2019 16:40:55 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1iKPsV-00022q-2b for pgsql-hackers@lists.postgresql.org; Tue, 15 Oct 2019 16:40:55 +0000 Received: from mail-io1-xd42.google.com ([2607:f8b0:4864:20::d42]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iKPsS-0006aI-Ae for pgsql-hackers@lists.postgresql.org; Tue, 15 Oct 2019 16:40:54 +0000 Received: by mail-io1-xd42.google.com with SMTP id b19so47471814iob.4 for ; Tue, 15 Oct 2019 09:40:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :user-agent; bh=F276Dfa/AF22Zx3z7sjw0SohOxC+L9LVp0q76iPKt8Q=; b=M0VnM87tn4xdnaxlvG6BcbIyoIAOiU0BLGX2Jcf1Idf61x5Kned3XK9l5BrfpREYub cgF8USHm7YEp7trla/MlFq+nlLL+AnXgQpcHzGHBNL9TI3nXcmIEUMRGPMcCFldIo9Bw diyOG+eBNwVCVfrMXKI5Rx8uZPDe59QHSZRchEHgUrICtlhXYaNf0EHxI7flSemm79SL SxoZKOqJNkObqtIXj2nwDapaQy/g6sk/dS7ZBG0FWPx0hvhF/p5l+mNrlz2Ie1ugsYum UKUrCFEskhdECzV58t3Xq49dN5T6/6we14MEN7xS+0WBTf4Axpm0iDztbwovHNRYNbUJ XuCQ== 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:user-agent; bh=F276Dfa/AF22Zx3z7sjw0SohOxC+L9LVp0q76iPKt8Q=; b=UM75OwS45leCk/x3/eluODuCKstJl8GGM3xyWocXAX+gIeMUeZa85gq2vhU7tbx68z nd3FJAs2bf7t5vvUpzcVgj05ooCQ7yAxWkm6CARFSkNnMnSPo26Ze1AlW4ViH3/Zj0qK IDlgTh0Swk4Ry1v+fdqTqZYgvme0T7jnwsT4exuwLZI7OyrS6KROMCcWkaA84isCMvPH GYjbOuftoBZbhOwbrpiBmvHw+TaqhH8sj+y8CP1cmb4tzpK7jpRABXGoRyiLASyhPKeZ DiONWyd56rpYeREHK20GE8xX2b0Dee/excoNwTcdo4qlbEVHbEvbsVQfOVR7ZmLmotuo +bvg== X-Gm-Message-State: APjAAAX8m6To26wJOVoGkvnDk9YwhnZFzaG18J3yqSZ+mC+e9JKf1ivK sY4aX89lHSOHqipv6DQVdWkO+ZRN1uk= X-Google-Smtp-Source: APXvYqz0APKFMXSmnpPWhEqc8oVagSB1TXhE0g78yDi3q3gkL3wJAHZE9K/WiyzgNQaKkoriMen3dg== X-Received: by 2002:a05:6638:928:: with SMTP id 8mr42312710jak.124.1571157650075; Tue, 15 Oct 2019 09:40:50 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id h4sm14524675iom.17.2019.10.15.09.40.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Oct 2019 09:40:49 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id E04FC801497; Tue, 15 Oct 2019 11:40:47 -0500 (CDT) Date: Tue, 15 Oct 2019 11:40:47 -0500 From: Justin Pryzby To: pgsql-hackers@lists.postgresql.org Cc: Michael Paquier , Peter Eisentraut , Andreas Karlsson Subject: v12.0: interrupt reindex CONCURRENTLY: ccold: ERROR: could not find tuple for parent of relation ... Message-ID: <20191015164047.GA22729@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On a badly-overloaded VM, we hit the previously-reported segfault in progress reporting. This left around some *ccold indices. I tried to drop them but: sentinel=# DROP INDEX child.alarms_null_alarm_id_idx1_ccold; -- child.alarms_null_alarm_time_idx_ccold; -- alarms_null_alarm_id_idx_ccold; ERROR: could not find tuple for parent of relation 41351896 Those are children of relkind=I index on relkind=p table. postgres=# CREATE TABLE t(i int)PARTITION BY RANGE(i); postgres=# CREATE TABLE t1 PARTITION OF t FOR VALUES FROM (1)TO(100); postgres=# INSERT INTO t1 SELECT 1 FROM generate_series(1,99999); postgres=# CREATE INDEX ON t(i); postgres=# begin; SELECT * FROM t; -- DO THIS IN ANOTHER SESSION postgres=# REINDEX INDEX CONCURRENTLY t1_i_idx; -- cancel this one ^CCancel request sent ERROR: canceling statement due to user request postgres=# \d t1 ... "t1_i_idx" btree (i) "t1_i_idx_ccold" btree (i) INVALID postgres=# SELECT inhrelid::regclass FROM pg_inherits WHERE inhparent='t_i_idx'::regclass; inhrelid t1_i_idx (1 row) Not only can't I DROP the _ccold indexes, but also dropping the table doesn't cause them to be dropped, and then I can't even slash dee them anymore: jtp=# DROP INDEX t1_i_idx_ccold; ERROR: could not find tuple for parent of relation 290818869 jtp=# DROP TABLE t; -- does not fail, but .. jtp=# \d t1_i_idx_ccold ERROR: cache lookup failed for relation 290818865 jtp=# SELECT indrelid::regclass, * FROM pg_index WHERE indexrelid='t1_i_idx_ccold'::regclass; indrelid | 290818865 indexrelid | 290818869 indrelid | 290818865 [...] Justin