3 ms·

Is there any documentation on the "extensibility patches"? What did you have to do to core Postgres to get this new approach to work?

• akorotkov 3y ago
  Please, check this. https://supabase.com/blog/postgres-pluggable-strorage https://supabase.com/blog/postgres-pluggable-strorage https://www.pgcon.org/events/pgcon_2023/schedule/session/470-future-of-table-access-methods/ https://www.pgcon.org/events/pgcon_2023/schedule/session/470... Pushing patches to PostgreSQL Core requires a lot of work. But there is a progress already: 5k lines patchset to PG 14, and 2k lines patchset to PG 16.
  • justinclift 3y ago
    Awesome. Thanks heaps for your efforts on this! Hopefully it all gets through the hurdles eventually, becoming a new storage engine shipped by default in PG. Maybe even becoming the new default. :)
  • ksec 3y ago
    >Please, check this. https://supabase.com/blog/postgres-pluggable-strorage https://supabase.com/blog/postgres-pluggable-strorage So 60% of code committed to PG 16 already?
    • mlyle 3y ago
      60% of the code needed to run it as a normal outside extension.
  • soleri17 3y ago
    good job!