| From: | Timur Magomedov <t(dot)magomedov(at)postgrespro(dot)ru> |
|---|---|
| To: | Peter Smith <smithpb2250(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me> |
| Cc: | "Aya Iwata (Fujitsu)" <iwata(dot)aya(at)fujitsu(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 |
| Date: | 2025-05-29 13:30:23 |
| Message-ID: | 1a7e91a87816ee2a9aa4d5559453baf2f3da9115.camel@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Peter,
I've noticed there are changes in Postgres code v4 patch that rollback
the commit [1]. That commit optimizes TupleHashEntryData struct size
and amount of memory allocations which improves performance (see
discussion [2]).
Can we use leave TupleHashEntryData as is and make new VCI-specific
struct that contains TupleHashEntryData member and an additional
pointer or make VCI use TupleHashEntryGetAdditional()?
[1]
https://www.postgresql.org/message-id/attachment/174581/v9-0004-Remove-additional-pointer-from-TupleHashEntryData.patch
[2]
https://www.postgresql.org/message-id/flat/817d244237878cebdff0bc363718feaf49a1ea7d.camel%40j-davis.com
-------
Regards,
Timur Magomedov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2025-05-29 13:42:30 | Re: PG 18 release notes draft committed |
| Previous Message | Tom Lane | 2025-05-29 13:21:48 | Re: autoprewarm_dump_now |