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 1iKGvl-0007DK-Fh for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Oct 2019 07:07:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iKGvk-00035L-0G for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Oct 2019 07:07:40 +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 1iKGvj-00035A-KN for pgsql-bugs@lists.postgresql.org; Tue, 15 Oct 2019 07:07:39 +0000 Received: from mail-wr1-x441.google.com ([2a00:1450:4864:20::441]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iKGvg-0001dP-6V for pgsql-bugs@lists.postgresql.org; Tue, 15 Oct 2019 07:07:38 +0000 Received: by mail-wr1-x441.google.com with SMTP id j11so22413764wrp.1 for ; Tue, 15 Oct 2019 00:07:35 -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:references:mime-version :content-disposition:in-reply-to:user-agent; bh=GFJZEgJDe91TBTa+7chJ3xczJ/hdTqnt0TvKxr7poXY=; b=r5MVPkkH+hm0n2qTUcD6G6EeK+Ap8aVLKEH9KUoqlqFhp2P1Ajd+Pr8yB8MRS2lfx1 DAdROKm2eNJ25khvRTbNTNJC/DrStklNpR4/YE7SUfj3wAb/QZN7IM5Le2PoeWAKrXuv lIVCayDj07hO8kS9jq3ReJmriHyBBAJrR6YFtuC8V7F4zkCjI/nBHOCtsQu8pKd4drvh SbFV+aeSBUtutRer7jNFMeyVW8CIPhCWMoVuO0xgEC+sAI66ZktJyYISBk8igjMDCd7u 5Y51XW+SPRq0AmE7J+8QjfMFYak7n+DklZwcGzgaM6VvC/6WaRjGxJwwZuPmyDxd5pJd Rzjw== 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=GFJZEgJDe91TBTa+7chJ3xczJ/hdTqnt0TvKxr7poXY=; b=fnj/87r5Q2BG042nEpv9otPaJVLUfLhcGk7vEvij9HwlWa5HqdYfX/VSc5zE/1j4f8 oYOgrAll+pDmxrjocBp8MbmUqy8328TeZWD5+KF/gFMEqA5ioD483U2RBHsGMwHiuj12 vBxXyStWNqAVu2MPiCJBfKv1/OmdWr+pDquiPWCzKFcSR3r0FgPUPrPgLFN+6Ce4U99V Od9gmnTJim4zlsFDK/BvonHf1CRbHIWEUw55T7kbRyEerVB9HbQIyXV1GjZ3KFB0Ze0C 5uO8zngdSbk4a0a1gzOPUIBSMi0mv9F/dQgwTzPCuQBrQwVPRRG3w2j3Js4r9PlKXmS4 G4xw== X-Gm-Message-State: APjAAAXZ+chszJvu4G0M3ClGgqKvHbkUM8KDk9ENLJ/uyQfDW6GO6yKN +FhboNsh7DNgo8QX5xw5oeJBtg== X-Google-Smtp-Source: APXvYqxhVmQdBeIIsOYbbZ3ANjgi5MJpKVcBA21uiHjwehIthDi/BWMIwdtxeYrynTKgWK0cI65BCw== X-Received: by 2002:a05:6000:12d1:: with SMTP id l17mr18702427wrx.2.1571123254231; Tue, 15 Oct 2019 00:07:34 -0700 (PDT) Received: from localhost (net-188-219-235-30.cust.vodafonedsl.it. [188.219.235.30]) by smtp.gmail.com with ESMTPSA id n14sm17925911wro.83.2019.10.15.00.07.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 15 Oct 2019 00:07:27 -0700 (PDT) Date: Tue, 15 Oct 2019 09:07:25 +0200 From: Tomas Vondra To: Justin Pryzby Cc: Tom Lane , Andres Freund , buschmann@nidsa.net, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Message-ID: <20191015070725.csmdmdvrlb6klwkg@development> References: <20191010163350.2rtcjtje6tkgilqi@development> <1542.1570738460@sss.pgh.pa.us> <20191010204022.6hiiubm2cueu3ghk@development> <20191013001032.lqrn4kqaovhrf77l@development> <17717.1570991208@sss.pgh.pa.us> <20191013203848.2eksimmpux3546wr@development> <27596.1571062600@sss.pgh.pa.us> <20191014163538.cqn6j4cl7s2mk2yz@development> <20191015001817.zei45apgpu5dzngr@development> <20191015044118.GO3599@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20191015044118.GO3599@telsasoft.com> User-Agent: NeoMutt/20180716 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Oct 14, 2019 at 11:41:18PM -0500, Justin Pryzby wrote: >On Tue, Oct 15, 2019 at 02:18:17AM +0200, Tomas Vondra wrote: >> On Mon, Oct 14, 2019 at 06:35:38PM +0200, Tomas Vondra wrote: >> >... >> > >> >Aha! I forgot we copy the necessary stuff into pg_attribute. Thanks for >> >clarifying, I'll polish and push the fix shortly. > >Perhaps it'd be worth creating a test for on-disk format ? > >Like a table with a column for each core type, which is either SELECTed from >after pg_upgrade, or pg_dump output compared before and after. > IMO that would be useful - we now have a couple of these checks for different data types (line, unknown, sql_identifier), with a couple of combinations each. And I've been looking if we do similar pg_upgrade tests, but I haven't found anything. I mean, we do pg_upgrade the cluster used for regression tests, but here we need to test a number of cases that are meant to abort the pg_upgrade. So we'd need a number of pg_upgrade runs, to test that. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services