Skip to main content
  • Questions and feedback: Ask in the Pinecone Discord community, where other users and the Pinecone team answer.
  • Bugs and feature requests: Open an issue in the pg_pinecone repository. To propose a code change, open an issue first so the approach can be agreed on before any work starts.
  • Security issues: Don’t open a public issue. Email security@pinecone.io, or follow the security policy to report it privately on GitHub.
  • Your Pinecone account or index: For a problem with the Pinecone index that the remote engine or full-text search uses, contact Pinecone Support.

Check your install

When something doesn’t work, run pinecone.doctor() first. It checks your install and says how to fix each problem it finds.
  1. If you upgraded from a version earlier than 0.13.0, update the extension so pinecone.doctor() is available:
    SQL
  2. Run the check. This query lists only the checks that need attention, so no rows means everything passed:
    SQL
  3. For each row, the hint column says how to fix that check. Fix rows with a status of fail first. Some warn rows are expected. For example, without an API key, the credentials check reports warn, which is fine if you bring your own vectors and use only the native engine.
On a server that can’t reach Pinecone, run pinecone.doctor(remote => false) to skip the request to Pinecone.

Check reference

The function runs with your role’s permissions. A check your role can’t read reports warn, not fail.

Report a bug

When you report a bug, include:
  • Your pg_pinecone and Postgres versions
  • Your operating system
  • The table’s engine
  • The full error message
  • The output of pinecone.doctor()
To find the versions, run:
SQL