Re: generic plans and "initial" pruning
От | Alvaro Herrera |
---|---|
Тема | Re: generic plans and "initial" pruning |
Дата | |
Msg-id | 20221201112106.gjlcv6nvndjbnoez@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: generic plans and "initial" pruning (Amit Langote <amitlangote09@gmail.com>) |
Ответы |
Re: generic plans and "initial" pruning
|
Список | pgsql-hackers |
On 2022-Dec-01, Amit Langote wrote: > Hmm, how about keeping the [Merge]Append's parent relation's RT index > in the PartitionPruneInfo and passing it down to > ExecInitPartitionPruning() from ExecInit[Merge]Append() for > cross-checking? Both Append and MergeAppend already have a > 'apprelids' field that we can save a copy of in the > PartitionPruneInfo. Tried that in the attached delta patch. Ah yeah, that sounds about what I was thinking. I've merged that in and pushed to github, which had a strange pg_upgrade failure on Windows mentioning log files that were not captured by the CI tooling. So I pushed another one trying to grab those files, in case it wasn't an one-off failure. It's running now: https://cirrus-ci.com/task/5857239638999040 If all goes well with this run, I'll get this 0001 pushed. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "Investigación es lo que hago cuando no sé lo que estoy haciendo" (Wernher von Braun)
В списке pgsql-hackers по дате отправления: