Skip to content

docs: document Additional Table Create SQL for creating indexes#2679

Open
jwhartley wants to merge 1 commit intomasterfrom
docs/additional-table-create-sql
Open

docs: document Additional Table Create SQL for creating indexes#2679
jwhartley wants to merge 1 commit intomasterfrom
docs/additional-table-create-sql

Conversation

@jwhartley
Copy link
Contributor

@jwhartley jwhartley commented Feb 16, 2026

Summary

  • Adds a usage section to the PostgreSQL materialization docs explaining how to use the additional_table_create_sql binding property for creating indexes
  • Adds the missing additional_table_create_sql property to the Databricks materialization docs bindings table, with a similar usage section
  • Includes a CREATE INDEX example (Postgres) and notes about when the SQL executes

Context

This field exists in config reference tables for Postgres-family connectors but the description ("Additional SQL statement(s) to be run in the same transaction that creates the table") doesn't make practical use cases obvious. The only existing usage example is on the TimescaleDB page (for hypertables).

A recent support thread showed this is a common source of confusion — customers aren't sure what the field is for or how to use it for things like creating indexes. Adding concrete examples should reduce repeat questions.

The Databricks connector also implements the field but it was missing from the docs entirely.

Test plan

  • Verify the Postgres and Databricks pages render correctly on the docs site

🤖 Generated with Claude Code

@jwhartley jwhartley requested review from aeluce and jonwihl February 16, 2026 01:33
@jwhartley
Copy link
Contributor Author

@github-actions
Copy link

github-actions bot commented Feb 16, 2026

PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://estuary.github.io/flow/pr-preview/pr-2679/

Built to branch gh-pages at 2026-02-16 01:49 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

The additional_table_create_sql binding property exists on several SQL
materializations but lacks guidance on practical use cases. This has
caused confusion in support — even internally — about what the field
does.

Add a usage section with index creation examples to the PostgreSQL and
Databricks materialization docs. For Databricks, also add the missing
property to the bindings reference table.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@jwhartley jwhartley force-pushed the docs/additional-table-create-sql branch from 0ee5941 to de0ccfb Compare February 16, 2026 01:47
Copy link
Collaborator

@aeluce aeluce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Did you want to update the Postgres materialization variants as well? If you didn't want to copy the new section to all of them, you could add a link to the binding property directed to the "Additional Table Create SQL" section in the main Postgres doc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants