Re: [WIP]Vertical Clustered Index (columnar store extension) - take2
От
Timur Magomedov
Тема
Re: [WIP]Vertical Clustered Index (columnar store extension) - take2
Дата
Msg-id
b0183172fbe8fbf4260d10df50a57127753eba68.camel@postgrespro.ru
Ответ на
Список
Дерево обсуждения
[WIP]Vertical Clustered Index (columnar store extension) - take2 "Aya Iwata (Fujitsu)" <iwata.aya@fujitsu.com>
Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Alvaro Herrera <alvherre@alvh.no-ip.org>
RE: [WIP]Vertical Clustered Index (columnar store extension) - take2 "Aya Iwata (Fujitsu)" <iwata.aya@fujitsu.com>
Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Yura Sokolov <y.sokolov@postgrespro.ru>
RE: [WIP]Vertical Clustered Index (columnar store extension) - take2 "Aya Iwata (Fujitsu)" <iwata.aya@fujitsu.com>
Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 Yura Sokolov <y.sokolov@postgrespro.ru>
Hello Peter! There is a code in vci_ros.c that initializes xl_heap_inplace xlrec. Comment says this code was taken from src/backend/access/heap/heapam.c. It was fine for Postgres 17 and earlier however struct xl_heap_inplace has 6 fields, not one since commit 243e9b40f1b2. So nmsgs field of xlrec has some random uninitialized value from stack. It goes to WAL and in case of big nmsgs it can cause segfault during server startup. Here are backtrace of a segfault while applying WAL on server startup and a patch that initializes all necessary fields of xlrec to avoid bad WAL records. -- Regards, Timur Magomedov
В списке pgsql-hackers по дате отправления