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 1iKjYQ-00006V-PW for pgsql-bugs@arkaria.postgresql.org; Wed, 16 Oct 2019 13:41:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iKjYP-00018T-DH for pgsql-bugs@arkaria.postgresql.org; Wed, 16 Oct 2019 13:41:29 +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 1iKjYP-000180-1f for pgsql-bugs@lists.postgresql.org; Wed, 16 Oct 2019 13:41:29 +0000 Received: from mail-wm1-x341.google.com ([2a00:1450:4864:20::341]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iKjYH-0003Yv-Rp for pgsql-bugs@lists.postgresql.org; Wed, 16 Oct 2019 13:41:27 +0000 Received: by mail-wm1-x341.google.com with SMTP id b24so2811807wmj.5 for ; Wed, 16 Oct 2019 06:41:21 -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=9u6V282VdquRB+rJ8tLJOGEV24Qf/qYYbQd/Vt8BuAQ=; b=njxIkdxgRY3OdWdxOwA1shrP3t68BDjjX79l9UPb2YcKlWty0yfvp4jG14lDJ9ZIuX WiPFwfSxUjOVNbGO9f/C79kJFWVDq44uOc7FECH1c8Yu+fiXXxt91GZZv8grUKGAQXg5 j8b0HiC8wJT4K4ik7OolvU5sg5/3dF6LPWw3CGN3svc5wQYVEy8l0NIkHp9OEHO4KwqR bCLTD84p+2YAv2y0xiC2FEjylyxQF/spd7x9ZIwQ3tsDtQvVI87jLBFhpAKSlJa7gX2z dCZpf+VjxLJW6pbIC1vYM0l/TrgZiOmD5nAscsvGuKcYhP0Tjijsb2mnadynwNBMfa+y fUXg== 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=9u6V282VdquRB+rJ8tLJOGEV24Qf/qYYbQd/Vt8BuAQ=; b=ZG9ofu9wp1h5uvseeH8ld2nhvi+8PSO9gvgIkYWdgbey9XR0329LfwKfLrjNiZ58cT fzLN8cu9+DtDEnOTMLli3EiRUW0j6j9rhtnTnDd9I3zJ1kbmj0dwJEVPXx/EwXj4aLdK K4vTwZKTxoa7ZxB45EhO+A8MgRHKQbXC56AKpAGdcFDc1LE50x2Abwt5M2ytrKrhDL6m khHYPoiUvtQifv8mWFvSECgT0aHxPsmkv3F11QhEnDOL+N3ydL6t2yMW7Jt8euhd1cYG wTcsLA8Jjf/ZvsJzeUuRxBZhgUIa1u/PbCJ2ojjny+ENHneqt3EuYlOOQYf6eLY/dYe3 sO4w== X-Gm-Message-State: APjAAAUM8mdJhy/W+B7Rz/dXjfKEabWKY1iv5jRA8beJhxazdrNAFnjO +iN6j93CQMuQZ5ez08/8rtPnAQ== X-Google-Smtp-Source: APXvYqy+TCOWTtO/U8i4kNKytOSRB6JQgyKS7KqDsYCqJrK3L4tS5t6LLoNPJzk6GNqihRRK0cN5ug== X-Received: by 2002:a7b:c3cf:: with SMTP id t15mr3421094wmj.85.1571233280232; Wed, 16 Oct 2019 06:41:20 -0700 (PDT) Received: from localhost (cst-prg-23-73.cust.vodafone.cz. [46.135.23.73]) by smtp.gmail.com with ESMTPSA id m16sm2319566wml.11.2019.10.16.06.41.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 16 Oct 2019 06:41:19 -0700 (PDT) Date: Wed, 16 Oct 2019 15:41:17 +0200 From: Tomas Vondra To: Tom Lane Cc: 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: <20191016134117.zfkonm6vtibxtiyq@development> References: <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> <20191016113344.ihrjpztakfppgilp@development> <11353.1571228877@sss.pgh.pa.us> <11665.1571232402@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <11665.1571232402@sss.pgh.pa.us> User-Agent: NeoMutt/20180716 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Oct 16, 2019 at 03:26:42PM +0200, Tom Lane wrote: >I wrote: >> Tomas Vondra writes: >>> I've just committed and pushed both fixes after some minor corrections. > >> Not quite right in 9.6 and before, according to crake. Looks like >> some issue with the CppAsString2'd constants? Did we even have >> CppAsString2 that far back? > >Yeah, we did. On closer inspection I suspect that we need to #include >some other file to get the RELKIND_ constants in the old branches. > Oh! Looking. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services