Extensions for Everyone

Static multi-page HTML deck. Open slide 00 and use the visible arrows or keyboard arrows to move through the talk.

00 · Part I. IntroductionExtensions for EveryoneExtensions are PostgreSQL's superpower, but only if users can actually get them.01 · Part I. IntroductionWho am IThis talk comes from maintaining Pigsty and the PostgreSQL extension delivery matrix.02 · Part I. IntroductionExtensibility MattersPostgreSQL wins through extensibility; delivery turns that into a systems problem.03 · Part I. IntroductionTwo Years LaterThe delivery layer is no longer just an idea; it has measurable operating shape.04 · Part I. IntroductionWho Benefits?Everyone means users, authors, vendors, and PostgreSQL hackers.05 · Part II : The Ecosystem LandscapeGalaxyThe ecosystem boundary is large and messy.06 · Part II : The Ecosystem LandscapeGitHub StarsGitHub stars are a useful but incomplete public attention signal.07 · Part II : The Ecosystem LandscapeStar TieringOrder-of-magnitude tiers make the visible ecosystem boundary legible.08 · Part II : The Ecosystem LandscapeThe Extension FunnelDiscovery is broad; delivery is narrower; usage is narrower again.09 · Part II : The Ecosystem LandscapeDimension AnalysisMetadata dimensions make the extension universe navigable.10 · Part III : The Delivery LayerThe Status QuoThe bottleneck is not package syntax; it is matrix coverage.11 · Part III : The Delivery LayerThe Trade-OffRust extension packages make build and delivery costs visible.12 · Part III : The Delivery LayerWhy Linux Native?Containers reduce the matrix, but native package delivery still matters.13 · Part III : The Delivery LayerPGEXT.CLOUDCatalog, repository, PIG CLI, and build infra are one delivery layer.14 · Part III : The Delivery LayerExtension CatalogStructured metadata is infrastructure.15 · Part III : The Delivery LayerCatalog DetailsThe catalog is a complete, queryable table of extension delivery metadata.16 · Part III : The Delivery LayerCatalog Page ViewsPage views are not usage, but they reveal attention.17 · Part III : The Delivery LayerRepositoryThe repository is one command with PIG, or plain APT/DNF when users want native control.18 · Part III : The Delivery LayerRepo Download StatsDownload data is useful, but incomplete and biased.19 · Part III : The Delivery LayerWhat We Can Still InferPartial telemetry can rank maintenance work, not extension importance.20 · Part III : The Delivery LayerThe CLI - PIGPIG turns native packages into a practical extension workflow.21 · Part IV Maintenance in the WildDimension Explosion!The 5 x 16 model is only the visible part of the matrix.22 · Part IV Maintenance in the WildPG Minor ABI BreakMinor-version ABI breaks are rare, but repositories still need an emergency path.23 · Part IV Maintenance in the WildOS Minor BreakA system-library jump can turn OS minor versions into build targets.24 · Part IV Maintenance in the WildRust ProblemsThe curated Rust set already spans five pgrx versions, with many more Rust projects still outside the catalog.25 · Part IV Maintenance in the WildBulky ExtensionsSome extension source archives are now measured in hundreds of MiB before the delivery matrix multiplies them.26 · Part IV Maintenance in the WildNaming ConflictsObject names are compatibility metadata, not just packaging labels.27 · Part IV Maintenance in the WildLibrary ConflictsPackage names, shared-library names, and CREATE EXTENSION names are separate compatibility surfaces.28 · Part IV Maintenance in the WildAPI BreakBuild failures can become ecosystem feedback for PostgreSQL hackers.29 · Part IV Maintenance in the WildPG 19 CompatibilityCore API changes become visible when real extensions stop compiling.30 · Part IV Maintenance in the WildKeeping It MaintainableA large extension matrix stays maintainable when packaging becomes a reviewed, repeatable loop.31 · Part IV Maintenance in the WildThree QuestionsThe closing question is which extension signals should become shared infrastructure.32 · Part IV Maintenance in the WildThank YouThank the audience and share contact details.