PostgreSQL Index Only Scan can NOT select ctid





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I have table A (id bigint, text text), and I have primary key btree on id.



Now I want to fetch ctid of records meet some condition like id = 823977776533426178.



However, even using pg_hint_plan to hint PostgreSQL to use Index Only Scan, it will always give me Index Scan, like the following:



/*+ IndexOnlyScan(a) */ explain analyze select ctid from a where id = 823977776533426178;
QUERY PLAN
----------------------------------------------------------------------------------------------------------
Index Scan using a_pkey on a (cost=0.14..8.16 rows=1 width=6) (actual time=0.038..0.039 rows=1 loops=1)
Index Cond: (id = '823977776533426178'::bigint)
Planning Time: 0.122 ms
Execution Time: 0.095 ms
(4 rows)


My understanding is ctid is the physical record id (block_no: record_offset) of each record and it must be included in any btree index, since any index will need this information to fetch the record from heap file.



Then why can't an index only scan return the ctid directly?
Is it just that PostgreSQL does not implement it that way?



BTW, my testing version is PostgreSQL-11.



Thank you!









share





























    0















    I have table A (id bigint, text text), and I have primary key btree on id.



    Now I want to fetch ctid of records meet some condition like id = 823977776533426178.



    However, even using pg_hint_plan to hint PostgreSQL to use Index Only Scan, it will always give me Index Scan, like the following:



    /*+ IndexOnlyScan(a) */ explain analyze select ctid from a where id = 823977776533426178;
    QUERY PLAN
    ----------------------------------------------------------------------------------------------------------
    Index Scan using a_pkey on a (cost=0.14..8.16 rows=1 width=6) (actual time=0.038..0.039 rows=1 loops=1)
    Index Cond: (id = '823977776533426178'::bigint)
    Planning Time: 0.122 ms
    Execution Time: 0.095 ms
    (4 rows)


    My understanding is ctid is the physical record id (block_no: record_offset) of each record and it must be included in any btree index, since any index will need this information to fetch the record from heap file.



    Then why can't an index only scan return the ctid directly?
    Is it just that PostgreSQL does not implement it that way?



    BTW, my testing version is PostgreSQL-11.



    Thank you!









    share

























      0












      0








      0








      I have table A (id bigint, text text), and I have primary key btree on id.



      Now I want to fetch ctid of records meet some condition like id = 823977776533426178.



      However, even using pg_hint_plan to hint PostgreSQL to use Index Only Scan, it will always give me Index Scan, like the following:



      /*+ IndexOnlyScan(a) */ explain analyze select ctid from a where id = 823977776533426178;
      QUERY PLAN
      ----------------------------------------------------------------------------------------------------------
      Index Scan using a_pkey on a (cost=0.14..8.16 rows=1 width=6) (actual time=0.038..0.039 rows=1 loops=1)
      Index Cond: (id = '823977776533426178'::bigint)
      Planning Time: 0.122 ms
      Execution Time: 0.095 ms
      (4 rows)


      My understanding is ctid is the physical record id (block_no: record_offset) of each record and it must be included in any btree index, since any index will need this information to fetch the record from heap file.



      Then why can't an index only scan return the ctid directly?
      Is it just that PostgreSQL does not implement it that way?



      BTW, my testing version is PostgreSQL-11.



      Thank you!









      share














      I have table A (id bigint, text text), and I have primary key btree on id.



      Now I want to fetch ctid of records meet some condition like id = 823977776533426178.



      However, even using pg_hint_plan to hint PostgreSQL to use Index Only Scan, it will always give me Index Scan, like the following:



      /*+ IndexOnlyScan(a) */ explain analyze select ctid from a where id = 823977776533426178;
      QUERY PLAN
      ----------------------------------------------------------------------------------------------------------
      Index Scan using a_pkey on a (cost=0.14..8.16 rows=1 width=6) (actual time=0.038..0.039 rows=1 loops=1)
      Index Cond: (id = '823977776533426178'::bigint)
      Planning Time: 0.122 ms
      Execution Time: 0.095 ms
      (4 rows)


      My understanding is ctid is the physical record id (block_no: record_offset) of each record and it must be included in any btree index, since any index will need this information to fetch the record from heap file.



      Then why can't an index only scan return the ctid directly?
      Is it just that PostgreSQL does not implement it that way?



      BTW, my testing version is PostgreSQL-11.



      Thank you!







      postgresql postgresql-performance postgresql-11





      share












      share










      share



      share










      asked 6 mins ago









      Qiushi BaiQiushi Bai

      83




      83






















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "182"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f234740%2fpostgresql-index-only-scan-can-not-select-ctid%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Database Administrators Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f234740%2fpostgresql-index-only-scan-can-not-select-ctid%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Liste der Baudenkmale in Friedland (Mecklenburg)

          Single-Malt-Whisky

          Czorneboh