| From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
|---|---|
| To: | Timur Magomedov <t(dot)magomedov(at)postgrespro(dot)ru> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, "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-06-12 07:08:40 |
| Message-ID: | CAHut+PsSTmpaFv8EZfyrXpi+e6Ft3bE5T6M_SOcVJB+hTKPc8w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 29, 2025 at 11:30 PM Timur Magomedov
<t(dot)magomedov(at)postgrespro(dot)ru> wrote:
>
> 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()?
>
Thanks for the report. This is fixed in v6.
======
Kind Regards,
Peter Smith.
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-06-12 07:09:35 | Re: Question on error code selection in conflict detection |
| Previous Message | Peter Smith | 2025-06-12 07:06:19 | Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 |