Re: index only scan question

Daniel Westermann wrote: > >I'd say the old index tuple was killed during the first scan: > >https://www.cybertec-postgresql.com/en/killed-index-tuples/ > > ... from your blog: "Whenever an index scan fetches a heap tuple only to find > that it is dead > (that the entire “HOT chain” of tuples is

Re: index only scan question

sorry, hit the wrong key >I'd say the old index tuple was killed during the first scan: >https://www.cybertec-postgresql.com/en/killed-index-tuples/ ... from your blog: "Whenever an index scan fetches a heap tuple only to find that it

Re: index only scan question

>I'd say the old index tuple was killed during the first scan: >https://www.cybertec-postgresql.com/en/killed-index-tuples/ ... from your blog: "Whenever an index scan fetches a heap tuple only to find that it is dead (that the entire “

Re: index only scan question

>I'd say the old index tuple was killed during the first scan: >https://www.cybertec-postgresql.com/en/killed-index-tuples/ Thanks Laurenz, I will check that

Re: index only scan question

>Am 09.11.2018 um 13:58 schrieb Daniel Westermann: >> Is that because of some sort of caching? >no, but vacuum updated the visibility map in the meantime. No, it do not, double checked that with: select pg_visibility_map('t1'::regclass, 0);

Re: index only scan question

Am 09.11.2018 um 13:58 schrieb Daniel Westermann: Is that because of some sort of caching? no, but vacuum updated the visibility map in the meantime. Regards, Andreas -- 2ndQuadrant - The PostgreSQL Support Company. www.2ndQuadrant.com

Re: index only scan question

Daniel Westermann wrote: > question: Given these steps: > > > postgres=# explain (analyze,buffers,costs off) select a from t1 where b = 5; > QUERY PLAN > -- > I

index only scan question

Hi quick question: Given these steps: postgres=# explain (analyze,buffers,costs off) select a from t1 where b = 5;     QUERY PLAN     --  Index Only Scan using i2 on t1