Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx
От | Tom Lane |
---|---|
Тема | Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx |
Дата | |
Msg-id | 411084.1698087308@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx
|
Список | pgsql-bugs |
Peter Geoghegan <pg@bowt.ie> writes: > On Mon, Oct 23, 2023 at 11:30 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> If this is because it's "only a hint" and doesn't have to be reliable, >> okay, but the documentation around indexUnchanged utterly fails to >> make that clear. I fear some poor index AM writer is going to get >> screwed big time when they assume this flag is good for more than >> heuristic decisions about when to do noncritical maintenance. > That's fair, though note that index_unchanged_by_update does at least > own the fact that it ignores the effects of BEFORE triggers in code > comments. It also doesn't care about predicates in partial indexes, > for reasons that are fairly specific to the way that the hint is > actually used on the nbtree side. Yeah, there are comments within index_unchanged_by_update about those things. What I'm unhappy about is that indexam.sgml's discussion of the indexUnchanged flag makes it sound far more trustworthy than it actually is. Somebody who just read that doco and didn't scour the underlying code would be badly misled. regards, tom lane
В списке pgsql-bugs по дате отправления: