| From: | Daniel Westermann <daniel(dot)westermann(at)dbi-services(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: index only scan question |
| Date: | 2018-11-09 14:59:29 |
| Message-ID: | AM4PR0901MB134677E9C9F2664B890F4763D2C60@AM4PR0901MB1346.eurprd09.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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/<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 dead, to be more precise), it marks the index tuple as “killed”. Then future index scans can simply ignore it.
I understand that, but in my case the chain is not dead so this does not explain the difference. Do I miss something?
Regards
Daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2018-11-09 15:51:33 | Re: index only scan question |
| Previous Message | Daniel Westermann | 2018-11-09 14:57:34 | Re: index only scan question |