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 1hbL7S-0006xO-65 for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Jun 2019 08:30:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hbL6S-0000wx-KU for pgsql-hackers@arkaria.postgresql.org; Thu, 13 Jun 2019 08:29:00 +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 1hbL6S-0000wq-6l for pgsql-hackers@lists.postgresql.org; Thu, 13 Jun 2019 08:29:00 +0000 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hbL6P-0005zN-P5 for pgsql-hackers@postgresql.org; Thu, 13 Jun 2019 08:28:59 +0000 Received: by mail-lj1-x22f.google.com with SMTP id v24so13293628ljg.13 for ; Thu, 13 Jun 2019 01:28:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=vW+VKF0pd5PIBZpnAVJhf/tc/mcHX0FNm2hs/E3CCQI=; b=QpI2u8lOO9rR2R6Y+aJD4yMrytcK51M/punEkSARfMcWcOGsNJ5GXalKvpXKLMUvZ6 YtmJfajkzRUAYRriF32DaBxiQoypyzhLq0qMosKHfGL1qaYLJxRSi/irFGkDSfr4+q5N rFcIIanjYdWFD4O/YDf5tKEafsdRehWkTAFDE+9qNhnQQfeiNUo5Nu8JDJKB820M00rj MfeHRjcFwGtYMahG5NvFihpzRjxir6ZxYHKQb6Dcl9AjUFuyFqmi8fe7XzLExhuLVibx 6pp/C2Sd1Kh7IWHFzHCmn9Ka7/FQPk+BbFjhkFXsP64K31+gszwMoEmfYNpUFEvmbr+n EE8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=vW+VKF0pd5PIBZpnAVJhf/tc/mcHX0FNm2hs/E3CCQI=; b=gHUbQi9lj8QosomWZhHpzn+DEr3+igsBHbCin0GITRqOeBc5WVkpuL/sOz/O9NMsDl iw/Nv2uAtaZDIvNRH/NKrZNYmi6ssu7NlBwy2p6jq5oV/XRSyrchxijxueHAjdSMgWk7 Yx09mxQqJSzh0simz2tsIA5NzqbRmJ+xXsfezsRfcfPVC+crxcstoKCpd2amOWPk1lHs 3RN9RjDJYaStEQHs/TJMqAenotfH2ED8RlNnHTHuzZr9lCYUQrhFLMMvb4CCxp30eJb7 yI3QXtBqcqav7isE6E50KAY7cBWnzxm7CGOgZ+jPi+7IR2+ClraINe1ucdrsLNMxictf pJMw== X-Gm-Message-State: APjAAAVF88gKqvAMmm+odqMJL9B2QLnbzEBWMI380GGPXgL1TrT1Dq2V BgIOjPDYL3Iz1WvB6ndFmLsMHtLdnnFP1A== X-Google-Smtp-Source: APXvYqyamaEoatCHxsHQ0KvOTn+DBhGzyrOUsZCzCEX/lktllpOG5aS+KTRtaR2Zna2lZt8sFC6gtA== X-Received: by 2002:a2e:981:: with SMTP id 123mr14627333ljj.66.1560414536077; Thu, 13 Jun 2019 01:28:56 -0700 (PDT) Received: from [1.0.0.7] ([178.155.4.56]) by smtp.gmail.com with ESMTPSA id r84sm489774lja.54.2019.06.13.01.28.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Jun 2019 01:28:55 -0700 (PDT) Subject: Re: Fix inconsistencies for v12 (pass 2) To: Michael Paquier Cc: Amit Kapila , pgsql-hackers , Andres Freund References: <20190613081007.GH1643@paquier.xyz> From: Alexander Lakhin Message-ID: Date: Thu, 13 Jun 2019 11:28:42 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <20190613081007.GH1643@paquier.xyz> Content-Type: multipart/mixed; boundary="------------71EF3284435520CC5DAAFBEC" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------71EF3284435520CC5DAAFBEC Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Hello Michael, 13.06.2019 11:10, Michael Paquier wrote: > On Wed, Jun 12, 2019 at 05:34:06PM +0300, Alexander Lakhin wrote: >> I can't see another inconsistencies for v12 for now, but there are some >> that appeared before. >> If this work can be performed more effectively or should be >> postponed/canceled, please let me know. > Note sure that it is much productive to have one patch with basically > one-liners in each one... Anyway.. As the proposed fixes are independent, I decided to separate them. I will make a single patch on next iteration. > All your suggestions are right. I do have one doubt for the > suggestion in execnodes.h: > @@ -1571,7 +1571,6 @@ typedef struct TidScanState > int tss_NumTids; > int tss_TidPtr; > ItemPointerData *tss_TidList; > - HeapTupleData tss_htup; > } TidScanState; > The last trace of tss_htup has been removed as of 2e3da03, and I see > no mention of it in the related thread. Andres, is that intentional > for table AMs to keep a trace of a currently-fetched tuple for a TID > scan or something that can be removed? The field is still > documented, so the patch is incomplete if we finish by removing the > field. And my take is that we should keep it. Yes, you're right. I've completed the patch for a possible elimination of the field. Best regards, Alexander --------------71EF3284435520CC5DAAFBEC Content-Type: text/x-patch; name="tss_htup.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="tss_htup.patch" diff --git a/src/include/nodes/execnodes.h b/src/include/nodes/execnodes.h index 99b9fa414f..03166754c0 100644 --- a/src/include/nodes/execnodes.h +++ b/src/include/nodes/execnodes.h @@ -1560,7 +1560,6 @@ typedef struct BitmapHeapScanState * NumTids number of tids in this scan * TidPtr index of currently fetched tid * TidList evaluated item pointers (array of size NumTids) - * htup currently-fetched tuple, if any * ---------------- */ typedef struct TidScanState @@ -1571,7 +1570,6 @@ typedef struct TidScanState int tss_NumTids; int tss_TidPtr; ItemPointerData *tss_TidList; - HeapTupleData tss_htup; } TidScanState; /* ---------------- --------------71EF3284435520CC5DAAFBEC--