| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Stefan Keller <sfkeller(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Chapman Flack <chap(at)anastigmatix(dot)net>, Oleg Ivanov <o(dot)ivanov(at)postgrespro(dot)ru>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ML-based indexing ("The Case for Learned Index Structures", a paper from Google) |
| Date: | 2021-04-22 03:39:33 |
| Message-ID: | 56C62A91-64F6-458B-AA7E-189A6FBD0329@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 21 апр. 2021 г., в 21:01, Stefan Keller <sfkeller(at)gmail(dot)com> написал(а):
>
> What's needed - and what many here as well as the "ML-In-Databases"
> paper from Kraska et al. (2021) are saying - is, that a new index
> (like a learned index) should be implemented as a PostgreSQL
> extension.
BTW, you don't have to implement index from scratch. You can take one of many existing and modify towards Learned Index.
Index contains many parts: scans, builds, vacuums, wal, opclasses etc. And simply adhering to API is a lot of work.
I'll be happy to help you to with formulating key differences and, probably, code of an extension.
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2021-04-22 04:06:50 | Re: Stale description for pg_basebackup |
| Previous Message | Etsuro Fujita | 2021-04-22 03:30:41 | Re: Asynchronous Append on postgres_fdw nodes. |