Re: The documentation for storage type 'plain' actually allows single byte header
От | Andres Freund |
---|---|
Тема | Re: The documentation for storage type 'plain' actually allows single byte header |
Дата | |
Msg-id | 20230115230320.d3mtlzek6dv7mgxx@awork3.anarazel.de обсуждение исходный текст |
Ответ на | Re: The documentation for storage type 'plain' actually allows single byte header (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: The documentation for storage type 'plain' actually allows single byte header
|
Список | pgsql-docs |
Hi, On 2023-01-15 16:40:27 -0500, Tom Lane wrote: > The documentation is correct, what is broken is the code. I'm not > sure when we broke it Looks to be an old issue, predating the slot type stuff. It reproduces at least as far back as 10. I've not thought through this fully. But after a first look, this might be hard to fix without incuring a lot of overhead / complexity. We check whether projection is needed between nodes with tlist_matches_tupdesc() - targetlists don't know about storage. And we decide whether we need to project in nodeModifyTuple solely based on /* Extract non-junk columns of the subplan's result tlist. */ foreach(l, subplan->targetlist) { TargetEntry *tle = (TargetEntry *) lfirst(l); if (!tle->resjunk) insertTargetList = lappend(insertTargetList, tle); else need_projection = true; } Greetings, Andres Freund
В списке pgsql-docs по дате отправления: