fix(checkpoint-postgres): ensure vector extension is created only if not exists

[mohankumarelec]

Thank you for contributing to LangGraph! Follow these steps to mark your pull request as ready for review. If any of these steps are not completed, your PR will not be considered for review.

• PR title: Follows the format: {TYPE}({SCOPE}): {DESCRIPTION}

  • Examples:
    • feat(core): add multi-tenant support
    • fix(cli): resolve flag parsing error
    • docs(openai): update API usage examples
  • Allowed {TYPE} values:
    • feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert, release
  • Allowed {SCOPE} values (optional):
    • langgraph, docs, cli, checkpoint, checkpoint-postgres, checkpoint-sqlite, prebuilt, scheduler-kafka, sdk-py
  • Once you've written the title, please delete this checklist item; do not include it in the PR.

• Description: Azure Postgres SQL server has a limitation when doing create extension vector is not exists, even though it manually created before on a schema.

• Issue: Even though CREATE EXTENSION vector is executed manually before, the permission issue arises. Putting it in an if else block solves the issue and its not a breaking change.

Because vector isn't a trusted extension, only members of "azure_pg_admin" are allowed to use CREATE EXTENSION vector
HINT: to learn how to allow an extension or see the list of allowed extensions, please refer to https://go.microsoft.com/fwlink/?linkid=2301063

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
langgraph-docs-preview	Ignored	Preview		Sep 16, 2025 2:23pm