| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Kamigishi Rei <iijima(dot)yun(at)koumakan(dot)jp>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: BUG #17245: Index corruption involving deduplicated entries |
| Date: | 2021-10-29 18:52:02 |
| Message-ID: | 202110291852.t6nxvmnhplnn@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2021-Oct-29, Peter Geoghegan wrote:
> However, this relation is a B-Tree index, where TIDs/page offset
> numbers are not stable at all.
>
> Almost all individual index tuple inserts onto a B-Tree page put the
> new index tuple "between" existing index tuples. This will "shift"
> whatever index tuples are to the right of the position of the new
> tuple.
Bah, of course. Sorry for the noise.
--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
"Puedes vivir sólo una vez, pero si lo haces bien, una vez es suficiente"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2021-10-29 18:57:51 | Re: BUG #17258: Unexpected results in CHAR(1) data type |
| Previous Message | Alvaro Herrera | 2021-10-29 18:50:32 | Re: BUG #17245: Index corruption involving deduplicated entries |