--- title: Google Cloud: Investing in the future of PostgreSQL —... description: Google Cloud recaps its PostgreSQL upstream contributions from January to September 2026, spanning four areas: logical replication and conflict management... canonical: https://daily.dev/posts/google-cloud-investing-in-the-future-of-postgresql-2026-highlights-t1wyfbzsp twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Google Cloud: Investing in the future of PostgreSQL — 2026 highlights | daily.dev og:description: Google Cloud recaps its PostgreSQL upstream contributions from January to September 2026, spanning four areas: logical replication and conflict management... og:url: https://daily.dev/posts/google-cloud-investing-in-the-future-of-postgresql-2026-highlights-t1wyfbzsp og:image: https://api.daily.dev/og/posts/t1WyfBzSP.png og:image:alt: Google Cloud: Investing in the future of PostgreSQL — 2026 highlights og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Google Cloud: Investing in the future of PostgreSQL — 2026 highlights **[Google Open Source Blog](https://daily.dev/sources/googleoss)** · 8 min read · 7 upvotes · 2 comments ## Summary Google Cloud recaps its PostgreSQL upstream contributions from January to September 2026, spanning four areas: logical replication and conflict management (including foundational conflict log table infrastructure slated for PG 20), core engine performance fixes (sequential scan overhead reduction, pg_promote timeout accuracy), catalog/collation/indexing bug fixes (large object access permissions, REINDEX CONCURRENTLY deferrable constraint bug, LIKE pattern backslash handling, DSM lock crash prevention), and ecosystem extension hardening for plpgsql_check, pgfincore, and pgtt. Individual engineers are credited for each patch, with links to the original mailing list threads and GitHub PRs. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the conflict log table infrastructure being added to PostgreSQL for logical replication? It is a new option in CREATE SUBSCRIPTION that establishes catalog structures and configuration hooks to direct replication conflict records into dedicated, queryable tables instead of requiring inspection of server logs or custom application handlers. This lays the groundwork for active-active multi-master replication with automatic conflict resolution. Provided no blocking issues arise, it is slated for inclusion in PostgreSQL 20. _Engineers tracking upcoming PostgreSQL replication features can follow ongoing coverage on daily.dev._ ### Why did REINDEX CONCURRENTLY cause constraint violations on deferrable unique constraints in PostgreSQL? The index_create_copy() function defaulted constraint flags to 0 when building a replacement index, which incorrectly set the immediate property to true instead of preserving deferrable behavior. This caused concurrent transactions to trigger constraint violations immediately rather than deferring verification until commit. The fix introduces an INDEX_CREATE_DEFERRABLE flag to correctly propagate the immediate=false property to transient copied indexes. _Developers debugging concurrent reindexing issues on deferrable constraints can find fixes like this tracked on daily.dev._ ### Why did loading plpgsql_check via shared_preload_libraries fail on PostgreSQL 14 and earlier? It could fail with shared memory lock errors due to missing or outdated named LWLock tranche registrations for the profiler funcs stats and profiler func stmts stats locks. The fix aligns pre-PG15 tranche initialization with modern shmem_request_hook patterns, guaranteeing safe shared memory allocation on older server versions. _Teams running plpgsql_check on legacy PostgreSQL versions can track extension compatibility fixes via daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@trevorsuna** · 0 upvotes > Conflict logging for logical replication could make multi-writer and migration setups far easier to operate, because today the failure evidence is often scattered across logs. I like that the roundup also credits smaller correctness fixes; catalog and collation bugs rarely look glamorous, but they protect the boring paths production depends on. **@pdfopsdev** · 0 upvotes > the seq scan overhead fix is the one I'd actually go read the thread on, that's been a quiet tax on any query planner that falls back to a full scan and it never got much attention outside pgsql-hackers. ## Similar posts on daily.dev - [Google Cloud Highlights Ongoing Work on PostgreSQL Core Capabilities](https://daily.dev/posts/google-cloud-highlights-ongoing-work-on-postgresql-core-capabilities-rgpoqn4hq) · InfoQ · 2 upvotes · 0 comments - [Google Cloud: PostgreSQL community contribution updates](https://daily.dev/posts/google-cloud-postgresql-community-contribution-updates-mqd2xo9zi) · Google Open Source Blog · 0 upvotes · 0 comments - [Contributions to the PostgreSQL Project](https://daily.dev/posts/contributions-to-the-postgresql-project-slhetdh8m) · Planet PostgreSQL · 1 upvotes · 0 comments --- Tags: [#open-source](https://daily.dev/tags/open-source), [#database](https://daily.dev/tags/database), [#postgresql](https://daily.dev/tags/postgresql), [#gcp](https://daily.dev/tags/gcp) [View this post on daily.dev](https://daily.dev/posts/google-cloud-investing-in-the-future-of-postgresql-2026-highlights-t1wyfbzsp) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Google Cloud: Investing in the future of PostgreSQL — 2026 highlights","url":"https://daily.dev/posts/google-cloud-investing-in-the-future-of-postgresql-2026-highlights-t1wyfbzsp","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/google-cloud-investing-in-the-future-of-postgresql-2026-highlights-t1wyfbzsp"},"datePublished":"2026-09-23T22:20:11.147Z","dateModified":"2026-09-23T22:20:34.069Z","description":"Google Cloud recaps its PostgreSQL upstream contributions from January to September 2026, spanning four areas: logical replication and conflict management...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/350f06264286ba7f308bd738d11cc473?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/350f06264286ba7f308bd738d11cc473?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Google Open Source Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Google Open Source Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8a87f457bf1a481b80c313f66a71200b","url":"https://daily.dev/sources/googleoss"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/google-cloud-investing-in-the-future-of-postgresql-2026-highlights-t1wyfbzsp","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":7},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"open-source,database,postgresql,gcp","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Google Open Source Blog","item":"https://daily.dev/sources/googleoss"},{"@type":"ListItem","position":3,"name":"Google Cloud: Investing in the future of PostgreSQL — 2026 highlights"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/google-cloud-investing-in-the-future-of-postgresql-2026-highlights-t1wyfbzsp","comment":[{"@type":"Comment","text":"Conflict logging for logical replication could make multi-writer and migration setups far easier to operate, because today the failure evidence is often scattered across logs. I like that the roundup also credits smaller correctness fixes; catalog and collation bugs rarely look glamorous, but they protect the boring paths production depends on.","datePublished":"2026-09-28T01:52:20.738Z","url":"https://daily.dev/posts/t1WyfBzSP#c-zPgegTLlF","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"}},{"@type":"Comment","text":"the seq scan overhead fix is the one I’d actually go read the thread on, that’s been a quiet tax on any query planner that falls back to a full scan and it never got much attention outside pgsql-hackers.","datePublished":"2026-09-26T18:07:23.484Z","url":"https://daily.dev/posts/t1WyfBzSP#c-07aV6wrDD","author":{"@type":"Person","name":"PDFops","url":"https://daily.dev/pdfopsdev","image":"https://media.daily.dev/image/upload/s---8isRBKc--/f_auto/v1782922291/avatars/avatar_orjMeK8QKaaVZwGq7ScPz?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/google-cloud-investing-in-the-future-of-postgresql-2026-highlights-t1wyfbzsp#faq","mainEntity":[{"@type":"Question","name":"What is the conflict log table infrastructure being added to PostgreSQL for logical replication?","acceptedAnswer":{"@type":"Answer","text":"It is a new option in CREATE SUBSCRIPTION that establishes catalog structures and configuration hooks to direct replication conflict records into dedicated, queryable tables instead of requiring inspection of server logs or custom application handlers. This lays the groundwork for active-active multi-master replication with automatic conflict resolution. Provided no blocking issues arise, it is slated for inclusion in PostgreSQL 20. Engineers tracking upcoming PostgreSQL replication features can follow ongoing coverage on daily.dev."}},{"@type":"Question","name":"Why did REINDEX CONCURRENTLY cause constraint violations on deferrable unique constraints in PostgreSQL?","acceptedAnswer":{"@type":"Answer","text":"The index_create_copy() function defaulted constraint flags to 0 when building a replacement index, which incorrectly set the immediate property to true instead of preserving deferrable behavior. This caused concurrent transactions to trigger constraint violations immediately rather than deferring verification until commit. The fix introduces an INDEX_CREATE_DEFERRABLE flag to correctly propagate the immediate=false property to transient copied indexes. Developers debugging concurrent reindexing issues on deferrable constraints can find fixes like this tracked on daily.dev."}},{"@type":"Question","name":"Why did loading plpgsql_check via shared_preload_libraries fail on PostgreSQL 14 and earlier?","acceptedAnswer":{"@type":"Answer","text":"It could fail with shared memory lock errors due to missing or outdated named LWLock tranche registrations for the profiler funcs stats and profiler func stmts stats locks. The fix aligns pre-PG15 tranche initialization with modern shmem_request_hook patterns, guaranteeing safe shared memory allocation on older server versions. Teams running plpgsql_check on legacy PostgreSQL versions can track extension compatibility fixes via daily.dev."}}]} ```