Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1enmZ3-0002IY-6I for pgsql-hackers@arkaria.postgresql.org; Mon, 19 Feb 2018 14:37:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1enmZ1-0005gJ-P1 for pgsql-hackers@arkaria.postgresql.org; Mon, 19 Feb 2018 14:37:07 +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 1enmZ1-0005g9-9U for pgsql-hackers@lists.postgresql.org; Mon, 19 Feb 2018 14:37:07 +0000 Received: from mail.postgrespro.ru ([93.174.131.138]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1enmYs-00014b-BA for pgsql-hackers@postgresql.org; Mon, 19 Feb 2018 14:37:05 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 2999721C1F4C; Mon, 19 Feb 2018 17:36:56 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=x tagged_above=-99 required=4 WHITELISTED tests=[] autolearn=unavailable Received: from [192.168.27.34] (gw.postgrespro.ru [93.174.131.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id E227221C1F4B; Mon, 19 Feb 2018 17:36:55 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1519051015; bh=tbcZXXC0q5ygwszcpaYvrB5B3pgfhkliwsfY3589/V4=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=b/XO5SHvqIiD1Ylz3N5HkvuGPMMuIK0h8tKLe8N/JsLPgUKBo9BHIrVf6tQt+C0ad fuECCilB38ycpQsbQdukVvyWYtCgVjgUHIZdMQsdFlrXlFPu4WBgqFpzSddgwMueZU RC8nft5gLaqLFin5XD+Pb8CyHvoXdZh2M2hZ7NCM= Subject: Re: CURRENT OF causes an error when IndexOnlyScan is used To: Tom Lane , Yugo Nagata Cc: pgsql-hackers@postgresql.org References: <20180201013349.937dfc5f.nagata@sraoss.co.jp> <20180201014444.f78358df.nagata@sraoss.co.jp> <22958.1517451171@sss.pgh.pa.us> From: Anastasia Lubennikova Message-ID: <97dc81d3-0ea9-3032-49d9-7983e35fb010@postgrespro.ru> Date: Mon, 19 Feb 2018 17:36:55 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <22958.1517451171@sss.pgh.pa.us> Content-Type: multipart/mixed; boundary="------------746C1EE18D729FC0B025CEA5" 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. --------------746C1EE18D729FC0B025CEA5 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 01.02.2018 05:12, Tom Lane: > Yugo Nagata writes: >> I'm sorry the patch attached in the previous mail is broken and >> not raises a compile error. I attached the fixed patch. > This patch is almost certainly wrong: you can't assume that the scan-level > state matches the tuple we are currently processing at top level. Any > sort of delaying action, for instance a sort or materialize node in > between, would break it. > > We need to either fix this aspect: > >>> IndexOnlyScan returns a virtual tuple that doesn't have system >>> column, so we can not get ctid in the same way of other plans. I'd like to propose the patch that fixes the issue. We already have a way to return heaptuple from IndexOnlyScan, but it was not applied to b-tree for some reason. Attached patch solves the reported bug. Moreover, it will come in handy for "index with included attributes" feature [1], where we can store long (and even TOASTed) attributes in indextuple. [1] https://commitfest.postgresql.org/17/1350/ -- Anastasia Lubennikova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company --------------746C1EE18D729FC0B025CEA5 Content-Type: text/x-patch; name="return_heaptuple_in_btree_indexonlyscan_v1.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="return_heaptuple_in_btree_indexonlyscan_v1.patch" diff --git a/src/backend/access/nbtree/nbtree.c b/src/backend/access/nbtree/nbtree.c index 8158508..db8a55c 100644 --- a/src/backend/access/nbtree/nbtree.c +++ b/src/backend/access/nbtree/nbtree.c @@ -374,6 +374,8 @@ btbeginscan(Relation rel, int nkeys, int norderbys) so->currTuples = so->markTuples = NULL; scan->xs_itupdesc = RelationGetDescr(rel); + scan->xs_hitupdesc = NULL; + scan->xs_hitup = NULL; scan->opaque = so; diff --git a/src/backend/access/nbtree/nbtsearch.c b/src/backend/access/nbtree/nbtsearch.c index 51dca64..dd3e8b2 100644 --- a/src/backend/access/nbtree/nbtsearch.c +++ b/src/backend/access/nbtree/nbtsearch.c @@ -25,6 +25,7 @@ #include "utils/tqual.h" +static HeapTuple _bt_fetch_tuple(IndexScanDesc scandesc); static bool _bt_readpage(IndexScanDesc scan, ScanDirection dir, OffsetNumber offnum); static void _bt_saveitem(BTScanOpaque so, int itemIndex, @@ -38,6 +39,31 @@ static bool _bt_endpoint(IndexScanDesc scan, ScanDirection dir); static void _bt_drop_lock_and_maybe_pin(IndexScanDesc scan, BTScanPos sp); static inline void _bt_initialize_more_data(BTScanOpaque so, ScanDirection dir); +/* + * Fetch all keys in tuple. + * Returns a new HeapTuple containing the originally-indexed data. + */ +static HeapTuple +_bt_fetch_tuple(IndexScanDesc scandesc) +{ + Relation index = scandesc->indexRelation; + Datum fetchatt[INDEX_MAX_KEYS]; + bool isnull[INDEX_MAX_KEYS]; + int i; + HeapTuple htuple; + + for (i = 0; i < index->rd_att->natts; i++) + { + fetchatt[i] = index_getattr(scandesc->xs_itup, i + 1, + scandesc->xs_itupdesc, &isnull[i]); + } + + htuple = heap_form_tuple(scandesc->xs_hitupdesc, fetchatt, isnull); + htuple->t_tableOid = scandesc->heapRelation->rd_id; + + + return htuple; +} /* * _bt_drop_lock_and_maybe_pin() @@ -1105,8 +1131,32 @@ readcomplete: /* OK, itemIndex says what to return */ currItem = &so->currPos.items[so->currPos.itemIndex]; scan->xs_ctup.t_self = currItem->heapTid; + if (scan->xs_want_itup) + { + if (!scan->xs_hitupdesc) + { + int natts = RelationGetNumberOfAttributes(scan->indexRelation); + int attno; + /* + * The storage type of the index can be different from the original + * datatype being indexed, so we cannot just grab the index's tuple + * descriptor. Instead, construct a descriptor with the original data + * types. + */ + scan->xs_hitupdesc = CreateTemplateTupleDesc(natts, false); + for (attno = 1; attno <= natts; attno++) + { + TupleDescInitEntry(scan->xs_hitupdesc, attno, NULL, + scan->indexRelation->rd_opcintype[attno - 1], + -1, 0); + } + } + scan->xs_itup = (IndexTuple) (so->currTuples + currItem->tupleOffset); + scan->xs_hitup = _bt_fetch_tuple(scan); + scan->xs_hitup->t_self = currItem->heapTid; + } return true; } @@ -1155,8 +1205,34 @@ _bt_next(IndexScanDesc scan, ScanDirection dir) /* OK, itemIndex says what to return */ currItem = &so->currPos.items[so->currPos.itemIndex]; scan->xs_ctup.t_self = currItem->heapTid; + if (scan->xs_want_itup) + { + if (!scan->xs_hitupdesc) + { + int natts = RelationGetNumberOfAttributes(scan->indexRelation); + int attno; + /* + * The storage type of the index can be different from the original + * datatype being indexed, so we cannot just grab the index's tuple + * descriptor. Instead, construct a descriptor with the original data + * types. + */ + scan->xs_hitupdesc = CreateTemplateTupleDesc(natts, false); + for (attno = 1; attno <= natts; attno++) + { + TupleDescInitEntry(scan->xs_hitupdesc, attno, NULL, + scan->indexRelation->rd_opcintype[attno - 1], + -1, 0); + } + } + scan->xs_itup = (IndexTuple) (so->currTuples + currItem->tupleOffset); + if (scan->xs_hitup) + pfree(scan->xs_hitup); + scan->xs_hitup = _bt_fetch_tuple(scan); + scan->xs_hitup->t_self = currItem->heapTid; + } return true; } @@ -1932,8 +2008,34 @@ _bt_endpoint(IndexScanDesc scan, ScanDirection dir) /* OK, itemIndex says what to return */ currItem = &so->currPos.items[so->currPos.itemIndex]; scan->xs_ctup.t_self = currItem->heapTid; + if (scan->xs_want_itup) + { + if (!scan->xs_hitupdesc) + { + int natts = RelationGetNumberOfAttributes(scan->indexRelation); + int attno; + /* + * The storage type of the index can be different from the original + * datatype being indexed, so we cannot just grab the index's tuple + * descriptor. Instead, construct a descriptor with the original data + * types. + */ + scan->xs_hitupdesc = CreateTemplateTupleDesc(natts, false); + for (attno = 1; attno <= natts; attno++) + { + TupleDescInitEntry(scan->xs_hitupdesc, attno, NULL, + scan->indexRelation->rd_opcintype[attno - 1], + -1, 0); + } + } + scan->xs_itup = (IndexTuple) (so->currTuples + currItem->tupleOffset); + if (scan->xs_hitup) + pfree(scan->xs_hitup); + scan->xs_hitup = _bt_fetch_tuple(scan); + scan->xs_hitup->t_self = currItem->heapTid; + } return true; } --------------746C1EE18D729FC0B025CEA5--