RDSC-6238: Clarify PostgreSQL publication safety for RDI and Redis Cloud

[ZdravkoDonev-redis]

Related ticket: RDSC-6238. The product advisory is implemented separately in core RDI #2905.

PostgreSQL sources can publish tables outside the RDI table selection when a publication uses FOR ALL TABLES. Application updates or deletes can then fail on published tables without replica identity, including tables RDI does not capture.

Changes

• Use an explicit table-list publication with publication.autocreate.mode: disabled in the Aurora/RDS preparation example. Explain filtered as the alternative when RDI has publication-management permissions; keep the product default unchanged.
• Add PostgreSQL publication settings to the Redis Cloud source preparation, pipeline creation, and quick-start instructions. Distinguish ingestion selection and Redis record keys from PostgreSQL publication membership and replica identity.
• Explain how administrators replace existing all-tables publications, coordinate other consumers, and preserve replication slots and RDI offsets. Switching to filtered alone cannot convert an all-tables publication, and leaving the old broad publication in place retains its write restrictions.
• Link REPLICA IDENTITY FULL to child-table nesting. Explain old row values and unchanged TOAST values instead of saying PostgreSQL events contain only changed fields.
• Add replica-identity and publication-maintenance guidance to Supabase preparation. Keep current and 1.19.1 database and denormalization guidance aligned.

Validation

• Checked publication behavior against PostgreSQL documentation/source and Debezium 3.0 documentation; inspected the Cloud quick-start Terraform example and PostgreSQL initialization scripts.
• Checked the rendered output of all 11 edited pages and 57 PostgreSQL, Cloud setup, and denormalization links/fragments. Current and 1.19.1 additions match after normalizing versioned links.
• No live database or Cloud pipeline qualification was run; this change updates documentation only.

---

Note

Low Risk
Documentation-only updates with no runtime or configuration code changes.

Overview
Documentation now explains how PostgreSQL logical replication publications interact with RDI table selection and why broad FOR ALL TABLES publications can break application writes on tables without replica identity.

The PostgreSQL preparation guide gains a checklist step and a large new section on replica identity (diagnostic SQL, fixes, TOAST/old-row behavior), publication.autocreate.mode (all_tables, filtered, disabled), admin-managed explicit publications, migrating off all-tables publications (coordination, slots/offsets), and a publication error FAQ. Aurora/RDS and Supabase examples switch from FOR ALL TABLES to table-list rdi_publication and point to collector/config.yaml settings.

Redis Cloud docs add a PostgreSQL publications section and clarify that console table selection and Redis keys do not change publication membership or PostgreSQL replica identity; quick start recommends publication.autocreate.mode: filtered. Denormalization/nesting text is tightened and cross-linked for when REPLICA IDENTITY FULL is required. Changes are mirrored in current and 1.19.1 RDI doc trees.

^{Reviewed by Cursor Bugbot for commit 01a1a43. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Staging links:
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/integrate/redis-data-integration/1.19.1/data-pipelines/data-denormalization/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/integrate/redis-data-integration/1.19.1/data-pipelines/prepare-dbs/aws-aurora-rds/aws-aur-pgsql/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/integrate/redis-data-integration/1.19.1/data-pipelines/prepare-dbs/postgresql/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/integrate/redis-data-integration/1.19.1/data-pipelines/prepare-dbs/supabase/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/integrate/redis-data-integration/data-pipelines/data-denormalization/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/integrate/redis-data-integration/data-pipelines/prepare-dbs/aws-aurora-rds/aws-aur-pgsql/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/integrate/redis-data-integration/data-pipelines/prepare-dbs/postgresql/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/integrate/redis-data-integration/data-pipelines/prepare-dbs/supabase/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/operate/rc/rdi/define/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/operate/rc/rdi/quick-start/
https://redis.io/docs/staging/docs/rdi-postgresql-publication-safety/operate/rc/rdi/setup/

[github-actions]

🧠 Redis Memory

Found 11 related items from repository history (2 new this commit):

• PR — Document PostgreSQL 18 support for RDI

  What changed

• PR — Document Supabase support for RDI

  What changed

• Commit — DOC-6878 Expand RDI FAQ CDC section with all supported databases

  DOC-6878 Expand RDI FAQ CDC section with all supported databases

• Commit — Document PostgreSQL 18 support for RDI

  Document PostgreSQL 18 support for RDI

• PR — DOC-6878 Expand RDI FAQ CDC section with all supported databases

  What

• Commit — DOC: clarify PostgreSQL publication setup for RDI

  DOC: clarify PostgreSQL publication setup for RDI

• PR — Document Supabase support for RDI

  What changed

• PR — DOC-6833: Fix four RDI Cloud doc issues from #rdi-cloud

  • Remove Active-Active from the 'multiple targets' use case sentence; add it as an explicit unsupported target topology under 'When not to u

• Commit — DOC: update versioned RDI PostgreSQL guidance

  DOC: update versioned RDI PostgreSQL guidance

• Commit — DOC: align Cloud PostgreSQL publications and replica identity guidance 🆕

  DOC: align Cloud PostgreSQL publications and replica identity guidance

• PR — WIP: Explain RDI CDC offsets and source retention 🆕

  What changes

Memory updated at 01a1a43

[andy-stark-redis]

LGTM

[ZdravkoDonev-redis]

Waiting on comments/approval from @ilianiliev-redis

[ZdravkoDonev-redis]

The replica identity preflight query is corrected in 01a1a43 on both current and 1.19.1 pages. It now checks that the primary or replica-identity index is live, valid, unique, immediate, and has no predicate. A deferrable primary key is therefore reported instead of being treated as a usable identity. The guidance calls this out explicitly.

The index rules were checked against PostgreSQL 16 RelationGetIndexList. Static diff checks passed; the SQL additions match between both page versions. Live SQL and Cloud qualification remain deferred, so this is not a runtime sign-off.

Related implementation is kept separate in RDSC-6238 / core RDI #2905. Remaining Aurora grant and networking corrections are separate drafts #4293 and #4294, under RDSC-6239.