- 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
remoteengine or full-text search uses, contact Pinecone Support.
Check your install
When something doesn’t work, runpinecone.doctor() first. It checks your install and says how to fix each problem it finds.
-
If you upgraded from a version earlier than 0.13.0, update the extension so
pinecone.doctor()is available:SQL -
Run the check. This query lists only the checks that need attention, so no rows means everything passed:
SQL
-
For each row, the
hintcolumn says how to fix that check. Fix rows with astatusoffailfirst. Somewarnrows are expected. For example, without an API key, thecredentialscheck reportswarn, which is fine if you bring your own vectors and use only thenativeengine.
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()
SQL