Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cOVjR-0003cq-G9 for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Jan 2017 20:30:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cOVjR-0005S3-1f for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Jan 2017 20:30:53 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cOVi1-00031z-Dr for pgsql-hackers@postgresql.org; Tue, 03 Jan 2017 20:29:25 +0000 Received: from mail-it0-x22c.google.com ([2607:f8b0:4001:c0b::22c]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cOVhx-0004wa-It for pgsql-hackers@postgresql.org; Tue, 03 Jan 2017 20:29:24 +0000 Received: by mail-it0-x22c.google.com with SMTP id c20so292599617itb.0 for ; Tue, 03 Jan 2017 12:29:21 -0800 (PST) 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:references:mime-version :content-disposition:in-reply-to:user-agent; bh=1uUSoLQRYpXCcYnTPKssx3H687S5vd/VNZenxwyb7PM=; b=yFLbN4UO2RzZBcrnrcocnDw3BHNo2jMhuwTgVGinP+hONQx/RDJQ4lJ7u8ZTFE0Ia8 OE+sb2fFraWvuN7CmD4ApA12I1536f7YIwJs9pOi39Zn2+Q/yaYHCOSarH5+LcYek2s/ eERoA7Y8ijysLdtw43rikrUo1q7pg2LVhR8j2EZmTR6aHp0g5O5w49m6CQl20m+4CpRM J+aJpPD7BN39u2eo9ONfHFQ6LT6EsfzTxyHHMB9xPdoLFf23g8UaC4+xEufBWT78JlFJ 511hidHeqGNBRfbMpKY20NmY5GkyTFsvom2zbFwyz7MbGBBAtTvWLPqQAq40u/uPHD1k kfaQ== 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:references :mime-version:content-disposition:in-reply-to:user-agent; bh=1uUSoLQRYpXCcYnTPKssx3H687S5vd/VNZenxwyb7PM=; b=dphoTtrDTfTPkx4Qn2TA9bIxuWfAK57M1GR3mRNQA3152cB4Hav+rTCmZPw9ndD0qj rYy3T/dr0C4riRruUfV51woK66TH8AvT46khrK2EmYJrqxigVICC5HSuOYYaArR+xf0g 7bj6JffSiFT2yHVv//L2Cyi3iFjvVLVbZMqZeA/gqrolz5yvUKHd0DudCoNOHN2BkrAC USUwNDXjiq0ubU0J59kv1j5cMCdEQQ6CdCm0gg4WDRjXKD0XXHVbgUYtbWovnd29ka3j EfF0t6NvfP9u0mqUEZkWr7WUDFrSo/XtC/K+BNSuMQKTJWByS+FzLUTDiwiUhUj6u8E5 yU7w== X-Gm-Message-State: AIkVDXKYbVg8pDX6R6hTFOt8P4Is7/6WLN8aoaiSxndKIP5TqjMhq4QxOCRwQKTUPvZ4WQ== X-Received: by 10.36.200.10 with SMTP id w10mr48843306itf.21.1483475360652; Tue, 03 Jan 2017 12:29:20 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id j96sm34240546ioo.29.2017.01.03.12.29.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Jan 2017 12:29:20 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id 6445D8014DC; Tue, 3 Jan 2017 14:29:19 -0600 (CST) Date: Tue, 3 Jan 2017 14:29:19 -0600 From: Justin Pryzby To: Tom Lane Cc: Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: ALTER TABLE .. ALTER COLUMN .. ERROR: attribute .. has wrong type Message-ID: <20170103202919.GU32031@telsasoft.com> References: <20170103003240.GM32031@telsasoft.com> <20170103165903.GP32031@telsasoft.com> <20170103185742.GQ32031@telsasoft.com> <28476.1483471956@sss.pgh.pa.us> <20170103194604.GR32031@telsasoft.com> <29101.1483473021@sss.pgh.pa.us> <20170103195709.GT32031@telsasoft.com> <30539.1483474695@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <30539.1483474695@sss.pgh.pa.us> User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On Tue, Jan 03, 2017 at 03:18:15PM -0500, Tom Lane wrote: > Justin Pryzby writes: > > (gdb) bt > > #3 0x000000000059d5ce in ATRewriteTable (tab=, OIDNewHeap=, lockmode=) at tablecmds.c:4152 > > I'm wondering if this represents some sort of out-of-sync condition > between the table and its child tables. We can't actually tell from > this trace which table is being processed. Could you try, from this > breakpoint, > > f 3 > p oldrel->rd_rel->relname (gdb) p oldrel->rd_rel->relname $1 = {data = "eric_umts_rnc_utrancell_201701", '\000' } -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers