Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 - Mailing list pgsql-hackers

From Timur Magomedov
Subject Re: [WIP]Vertical Clustered Index (columnar store extension) - take2
Date
Msg-id 9bebf705a4565fad027dda4ed09df020c94270b9.camel@postgrespro.ru
Whole thread Raw
In response to RE: [WIP]Vertical Clustered Index (columnar store extension) - take2  ("Aya Iwata (Fujitsu)" <iwata.aya@fujitsu.com>)
Responses Re: [WIP]Vertical Clustered Index (columnar store extension) - take2
List pgsql-hackers
Hello, Iwata-san.
> > 2. VCI has own Change Data Capture method. It doesn't use triggers
> > either logical replication for CDC, it uses IAM and homegrown hooks
> > in
> > heapam.c. Probably VCI-style CDC could be separated to its own
> > patch
> > for review and used in other extensions too.
>
> Could you elaborate a bit more on your thoughts regarding this?
> For example, what kind of hook functionality is thought to be useful?
> It's helpful if we decide hooks are really needed after some
> research,
> and we have to propose them separately.

All changes to core PostgreSQL code is currently maintained in a single
VCI-changes-to-postgres-core patch. It would be probably simpler to
review and accept if CDC patch was separated on its own. It would
contain hooks and anything else which allows VCI (or possibly any other
index) to get fresh data from table. Maybe we even don't need some
hooks but can extend IAM API instead.
--
Regards,
Timur Magomedov



pgsql-hackers by date:

Previous
From: Mark Wong
Date:
Subject: Re: Recommended TPC-DS tools/setup for PostgreSQL benchmarking?
Next
From: Aditya Kamath
Date:
Subject: RE: AIX support