Horton

Re: [WIP]Vertical Clustered Index (columnar store extension) - take2

Peter Smith <smithpb2250@gmail.com>

View thread
From: Peter Smith <smithpb2250@gmail.com>
To: Timur Magomedov <t.magomedov@postgrespro.ru>
Cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>, Tomas Vondra <tomas@vondra.me>, "Aya Iwata (Fujitsu)" <iwata.aya@fujitsu.com>, Japin Li <japinli@hotmail.com>, shveta malik <shveta.malik@gmail.com>
Date: 2025-11-13T07:02:20Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Mark ItemPointer arguments as const throughout

  2. Reorganize GUC structs

  3. Eliminate XLOG_HEAP2_VISIBLE from vacuum phase III

  4. Update various forward declarations to use typedef

  5. Pathify RHS unique-ification for semijoin planning

  6. Revert "Don't lock partitions pruned by initial pruning"

  7. For inplace update, send nontransactional invalidations.

  8. Remove nearly-unused SizeOfIptrData macro.

Hi Timur,

Thank you so much for your continued interest in this patch and for
taking the time to report these bugs! It is really appreciated and
your info has been recorded so it won't be forgotten.

Recent work and focus:

* As you might have seen, there have been many changes to master
lately, so I've been rebasing VCI to keep everything building cleanly.
Good news - the existing tests are now working again (locally) after
failing on -hackers for the past couple of weeks. I'm planning to post
the updated patches before the end of this week.

* Once that's done, my next priority is to split the patch 0002 into
smaller, more manageable pieces for easier review.

In other words, it is going to take a little while before I can circle
back to help investigate intermittent bugs.

Regarding your questions:

On Thu, Nov 13, 2025 at 3:11 AM Timur Magomedov
<t.magomedov@postgrespro.ru> wrote:
>
...
> I don't understand yet how to fix this and the reproducing is clunky so
> any ideas are welcome.
> Does this reproduce on your system too? Is it some known problem?
>

I'll follow your reproduction steps when I have a chance and get back to you.

I am not aware that this is a known problem.

~~

Thanks again. Sorry I can't be of more immediate help.

======
Kind Regards,
Peter Smith.
Fujitsu Australia