Decompose Notion PostgreSQL seller messaging after #149 by brianamarie · Pull Request #173 · percona/percona-messaging

brianamarie · 2026-06-01T12:24:18Z

Summary

This PR picks up the Notion PostgreSQL seller work after #149 merged. It adds field-facing conversation starters and public resources to the PostgreSQL product page, and folds extension Support scope into the existing pillar bullets instead of creating a separate inventory.

What changed

products/postgresql/messaging.md

Conversation starters and public resources (no elevator pitch or purpose; the intro already covers that)
Clearer extension scope in context: Citus and timescale (advisory, not packaged), barman/repmgr, pgvector/pgvectorscale, pg_stat_kcache/pg_wait_sampling
Link to the public Support for PostgreSQL page

use-cases-value-pillars/future-readiness-ai.md

pgvectorscale is advisory and not packaged; Percona is an ops partner for pgvector, not an AI platform vendor

products/README.md and offerings/README.md

Short routing note: engine-specific expert coverage belongs under products/{engine}/, not in cross-engine offering files

Context

#149 handled May 2026 product facts. This PR adds the seller decomposition from Notion batch-31 that did not land in closed #145: starters, resources, and extension/advisory scope in the right modules.

We intentionally did not add a PostgreSQL extension table to expert-support.md. Offering files stay cross-engine; PostgreSQL-specific scope lives on the product page.

Out of scope

Feature comparison tables (still need a PDF/table source)
Operator 3.0 messaging (Operators cloud-native framing and PostgreSQL Operator 3.0.0 messaging #156)
Support tier or pricing detail (internal packaging)

Made with Cursor

Add conversation starters and public resources to products/postgresql/ messaging.md; keep extension and advisory Support scope in product pillar bullets. Align pgvectorscale advisory wording in future-readiness-ai and document engine-specific expert-coverage routing in products/ and offerings/ README files. Co-authored-by: Cursor <cursoragent@cursor.com>

github-actions · 2026-06-01T12:24:33Z

New File Governance Check

No added markdown files detected.

Doc Coverage Check

No new markdown docs detected.

Duplicate Detector

Changed markdown docs: 4

No significant overlap detected.

Manual waiver commands (maintainers)

/governance-ok all or /governance-all
/governance-ok new-file, /governance-ok doc-coverage, /governance-ok duplicate
/governance-reset all or /governance-reset with the same token

Waiver JSON is stored in a hidden PR comment (messaging-governance-waiver-data:v1), same pattern as Impact Check.

_{Triggered by pull_request. Workflow content-governance-checks.yml. Docs: AUTOMATION.md, automation/README.md.}

github-actions · 2026-06-01T12:24:34Z

Messaging Smart Suggestions

File	Why impacted	Claim	Confidence
`use-cases-value-pillars/cost-optimization.md`	PostgreSQL cost/TCO claims usually impact shared value proof messaging.	cost	0.95
`framework/core-positioning.md`	PostgreSQL cost/TCO claims usually impact shared value proof messaging.	cost	0.95
`products/postgresql/messaging.md`	PostgreSQL cost/TCO claims usually impact shared value proof messaging.	cost	0.65
`reference/canonical-naming.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`reference/banned-terms.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`framework/core-positioning.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`framework/why-percona.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`offerings/expert-support.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`offerings/expertops.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`offerings/expert-consulting.md`	License and open source positioning changes are cross-cutting.	cost	0.95
`offerings/expert-support.md`	Offering naming updates should stay aligned across offering pages.	cost	0.95
`offerings/expertops.md`	Offering naming updates should stay aligned across offering pages.	cost	0.95
`offerings/expert-consulting.md`	Offering naming updates should stay aligned across offering pages.	cost	0.95
`reference/canonical-naming.md`	Offering naming updates should stay aligned across offering pages.	cost	0.95
`framework/core-positioning.md`	Offering naming updates should stay aligned across offering pages.	cost	0.95
`framework/core-positioning.md`	Product messaging modules often need checks against company framing and shared pillars or offerings.	cost	0.95
`framework/why-percona.md`	Product messaging modules often need checks against company framing and shared pillars or offerings.	cost	0.95

Only auto-apply suggestions at high confidence with reviewer approval.

_{Triggered by pull_request. Workflow smart-suggestions.yml. Docs: AUTOMATION.md, automation/README.md.}

github-actions · 2026-06-01T12:24:36Z

{
"all": true,
"paths": [],
"reset_paths": []
}

janwieremjewicz

LGTM

janwieremjewicz · 2026-06-03T12:35:20Z

 Percona enables AI, vector search, and hybrid data workloads through open, secure, and portable database architectures. Customers can modernize existing systems for emerging workloads without replatforming or lock-in.

- **AI-ready databases:** Percona packages [pgvector](https://www.percona.com/blog/pgvector-the-critical-postgresql-component-for-your-enterprise-ai-strategy/) for PostgreSQL alongside other tested distribution components ([third-party components](https://docs.percona.com/postgresql/18/third-party.html)). Extensions such as pgvectorscale ship only where documented for a release ([release notes](https://docs.percona.com/postgresql/latest/release-notes/release-notes.html)), which ties AI workload planning to the builds organizations install. Expert Support and consulting cover PostgreSQL and pgvector performance and operations; embedding model selection and LLM application design remain with development teams.
+- **AI-ready databases:** Percona packages [pgvector](https://www.percona.com/blog/pgvector-the-critical-postgresql-component-for-your-enterprise-ai-strategy/) for PostgreSQL alongside other tested distribution components ([third-party components](https://docs.percona.com/postgresql/18/third-party.html)). Percona Expert Support includes advisory guidance for pgvector production tuning. Percona focuses on PostgreSQL performance, scalability, and security for vector workloads, not embedding-model or LLM application design. pgvectorscale is available through advisory Support tiers and is not packaged in Percona Distribution for PostgreSQL.


Having read this I think these days it's good to say that real experts will support you, not only AI agents :)

brianamarie · 2026-06-04T09:27:53Z

/impact-ok all

github-actions · 2026-06-04T09:28:09Z

🤖 Recorded /impact-ok all. Re-running Impact Check with updated waivers.

github-actions · 2026-06-04T09:28:10Z

brianamarie · 2026-06-04T09:28:29Z

 - Logical replication for migration and scale-out: Percona Distribution for PostgreSQL on PostgreSQL 18 supports parallel logical replication for faster initial data synchronization during replica build and major-version migration, reducing cutover risk and replication catch-up time.
 - Built-in replication lag monitoring: PostgreSQL provides native, accurate replication lag tracking through `pg_stat_wal_receiver` and WAL LSN comparison, without requiring external heartbeat tooling. PMM surfaces this data via the `pg_custom_stat_wal_receiver_lag_bytes` metric (sourced from `postgres_exporter`). Teams migrating from MySQL (where external tools like pt-heartbeat are common for lag measurement) gain this capability out of the box with PostgreSQL.
- Horizontal scale and legacy tooling: Expert Support and consulting cover Citus sharding coordinated with Patroni HA on customer deployments where Citus runs alongside the distribution stack (Citus is not packaged in the standard distribution build; see [third-party components](https://docs.percona.com/postgresql/18/third-party.html)). Advisory Expert Support is also available for estates that still run barman or repmgr alongside PostgreSQL where migration to pgBackRest and Patroni is phased.
+- Horizontal scale and legacy tooling: Expert Support and consulting cover Citus sharding and timescale time-series workloads on customer-managed PostgreSQL coordinated with Patroni HA where those extensions run alongside the distribution stack (neither Citus nor timescale is packaged in the standard distribution build; see [third-party components](https://docs.percona.com/postgresql/18/third-party.html)). Advisory Expert Support is also available for estates that still run barman or repmgr alongside PostgreSQL where migration to pgBackRest and Patroni is phased.


@andrey-glazkov, could you please review these details on our support offerings? I don't want to overclaim.

brianamarie requested review from ImTheKai and janwieremjewicz as code owners June 1, 2026 12:24

brianamarie assigned janwieremjewicz Jun 1, 2026

brianamarie added messaging Improvements or additions to messaging Area: PostgreSQL PostgreSQL ecosystem messaging (products/postgresql/). labels Jun 1, 2026

janwieremjewicz previously approved these changes Jun 3, 2026

View reviewed changes

brianamarie added Content & messaging Canonical copy, products, use cases, case studies, and narrative. Inbound Inbound: ships, GTM, or external requests driving updates to canonical messaging in this repo. and removed messaging Improvements or additions to messaging labels Jun 4, 2026

Update products/postgresql/messaging.md

6d511ab

brianamarie dismissed janwieremjewicz’s stale review via 6d511ab June 4, 2026 09:25

Merge branch 'main' into postgresql-notion-decompose

044a905

brianamarie commented Jun 4, 2026

View reviewed changes

brianamarie requested a review from andrey-glazkov June 4, 2026 09:28

brianamarie assigned andrey-glazkov and unassigned janwieremjewicz Jun 4, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Decompose Notion PostgreSQL seller messaging after #149#173

Decompose Notion PostgreSQL seller messaging after #149#173
brianamarie wants to merge 3 commits into
mainfrom
postgresql-notion-decompose

brianamarie commented Jun 1, 2026

Uh oh!

github-actions Bot commented Jun 1, 2026

Uh oh!

github-actions Bot commented Jun 1, 2026

Uh oh!

github-actions Bot commented Jun 1, 2026 •

edited

Loading

Uh oh!

janwieremjewicz left a comment

Uh oh!

Uh oh!

janwieremjewicz Jun 3, 2026

Uh oh!

brianamarie commented Jun 4, 2026

Uh oh!

github-actions Bot commented Jun 4, 2026

Uh oh!

github-actions Bot commented Jun 4, 2026 •

edited

Loading

Uh oh!

brianamarie Jun 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

brianamarie commented Jun 1, 2026

Summary

What changed

Context

Out of scope

Uh oh!

github-actions Bot commented Jun 1, 2026

New File Governance Check

Doc Coverage Check

Duplicate Detector

Manual waiver commands (maintainers)

Uh oh!

github-actions Bot commented Jun 1, 2026

Messaging Smart Suggestions

Uh oh!

github-actions Bot commented Jun 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

janwieremjewicz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

janwieremjewicz Jun 3, 2026

Choose a reason for hiding this comment

Uh oh!

brianamarie commented Jun 4, 2026

Uh oh!

github-actions Bot commented Jun 4, 2026

Uh oh!

github-actions Bot commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Messaging Impact Check

postgres-cost-claim (WARN)

licensing-or-open-source-claims (WARN)

offering-name-or-tier-change (WARN)

product-messaging-module-touch (WARN)

Uh oh!

brianamarie Jun 4, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

github-actions Bot commented Jun 1, 2026 •

edited

Loading

github-actions Bot commented Jun 4, 2026 •

edited

Loading