@mastra/pg 1.33.0-alpha.0 → 1.33.0-alpha.2

package/dist/_types/@internal_core/dist/knowledge-compat/index.d.ts

@@ -1,4 +1,3 @@
-//#region src/knowledge-compat/index.d.ts
 export declare const KNOWLEDGE_V2_CORE_FEATURE = "knowledge-v2";
 export declare const KNOWLEDGE_STORAGE_CONTRACT_VERSION: 2;
 export declare const KNOWLEDGE_STORAGE_SCHEMA_VERSION: 2;
@@ -589,6 +588,5 @@ interface KnowledgeV2Core {
 }
 export declare function assertKnowledgeV2CoreSupport(features: ReadonlySet<string>): void;
 export declare function createKnowledgeV2CoreLoader(features: ReadonlySet<string>, loadStorageModule: () => Promise<unknown>): () => Promise<KnowledgeV2Core>;
-//#endregion
 export {};
 //# sourceMappingURL=index.d.ts.map

package/dist/_types/@internal_core/dist/memory/index.d.ts

@@ -1,4 +1,3 @@
-//#region src/memory/index.d.ts
 /**
  * Shared rules for observational memory lifecycle writes. Every storage adapter applies
  * these inside its own atomic section (lock, transaction, or conditional update), so the
@@ -97,5 +96,4 @@ export declare function assertActiveObservationsApplied(result: UpdateActiveObse
  * (equal, or only appended to since).
  */
 export declare function isAppendOnlySince(storedObservations: string, snapshotObservations: string): boolean;
-//#endregion
 //# sourceMappingURL=index.d.ts.map

package/dist/docs/SKILL.md

@@ -3,7 +3,7 @@ name: mastra-pg
 description: Documentation for @mastra/pg. Use when working with @mastra/pg APIs, configuration, or implementation.
 metadata:
   package: "@mastra/pg"
-  version: "1.33.0-alpha.0"
+  version: "1.33.0-alpha.2"
 ---
 
 ## When to use

package/dist/docs/assets/SOURCE_MAP.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.33.0-alpha.0",
+  "version": "1.33.0-alpha.2",
   "package": "@mastra/pg",
   "exports": {},
   "modules": {}

package/dist/docs/references/docs-memory-semantic-recall.md

@@ -4,7 +4,11 @@
 
 # Semantic recall
 
-If you ask your friend what they did last weekend, they will search in their memory for events associated with "last weekend" and then tell you what they did. That's sort of like how semantic recall works in Mastra.
+Semantic recall is a built-in form of Retrieval-Augmented Generation (RAG) for agent memory. When a user sends a message, Mastra searches earlier messages for ones with a similar meaning and adds the most relevant ones to the agent's context.
+
+Matching on meaning matters because people often remember the idea behind something, not the exact words they used. A user might ask "What did we decide about the refund?" after originally writing "Let's give them their money back." A keyword search misses that connection, but semantic recall finds it.
+
+Use semantic recall when your agent needs details from earlier in a long conversation, or from a user's other conversations, that are no longer in [recent message history](https://mastra.ai/docs/memory/message-history).
 
 > **📹 Watch:** Watch [Mastra semantic recall](https://www.youtube.com/watch?v=UVZtK8cK8xQ\&pp=ygUVbWFzdHJhIHdvcmtpbmcgbWVtb3J5) to see how agents retrieve relevant messages from past conversations.
 

package/dist/docs/references/integrations-databases-dynamodb.md

@@ -50,7 +50,7 @@ bun add @mastra/dynamodb@latest
 
 Before using this package, you **must** create a DynamoDB table with a specific structure, including primary keys and Global Secondary Indexes (GSIs). This adapter expects the DynamoDB table and its GSIs to be provisioned externally.
 
-Detailed instructions for setting up the table using AWS CloudFormation or AWS CDK are available in [TABLE\_SETUP.md](https://github.com/mastra-ai/mastra/blob/main/stores/dynamodb/TABLE_SETUP.md). Please ensure your table is configured according to those instructions before proceeding.
+Detailed instructions for setting up the table using AWS CloudFormation or AWS CDK are available in [TABLE_SETUP.md](https://github.com/mastra-ai/mastra/blob/main/stores/dynamodb/TABLE_SETUP.md). Please ensure your table is configured according to those instructions before proceeding.
 
 ## Usage
 
@@ -122,7 +122,7 @@ For local development, you can use [DynamoDB Local](https://docs.aws.amazon.com/
 
 **config.credentials** (`object`): AWS credentials object with accessKeyId and secretAccessKey. If not provided, the AWS SDK will attempt to source credentials from environment variables, IAM roles (e.g., for EC2/Lambda), or the shared AWS credentials file.
 
-**config.ttl** (`object`): TTL (Time To Live) configuration for automatic data expiration. Configure per entity type: thread, message, trace, eval, workflow\_snapshot, resource, score. Each entity config includes: enabled (boolean), attributeName (string, default: 'ttl'), defaultTtlSeconds (number).
+**config.ttl** (`object`): TTL (Time To Live) configuration for automatic data expiration. Configure per entity type: thread, message, trace, eval, workflow_snapshot, resource, score. Each entity config includes: enabled (boolean), attributeName (string, default: 'ttl'), defaultTtlSeconds (number).
 
 ## TTL (time to live) configuration
 
@@ -254,7 +254,7 @@ The IAM role or user executing the code needs appropriate permissions to interac
 
 Before diving into the architectural details, keep these key points in mind when working with the DynamoDB storage adapter:
 
-- **External Table Provisioning:** This adapter _requires_ you to create and configure the DynamoDB table and its Global Secondary Indexes (GSIs) yourself, prior to using the adapter. Follow the guide in [TABLE\_SETUP.md](https://github.com/mastra-ai/mastra/blob/main/stores/dynamodb/TABLE_SETUP.md).
+- **External Table Provisioning:** This adapter _requires_ you to create and configure the DynamoDB table and its Global Secondary Indexes (GSIs) yourself, prior to using the adapter. Follow the guide in [TABLE_SETUP.md](https://github.com/mastra-ai/mastra/blob/main/stores/dynamodb/TABLE_SETUP.md).
 - **Single-Table Design:** All Mastra data (threads, messages, etc.) is stored in one DynamoDB table. This is a deliberate design choice optimized for DynamoDB, differing from relational database approaches.
 - **Understanding GSIs:** Familiarity with how the GSIs are structured (as per `TABLE_SETUP.md`) is important for understanding data retrieval and potential query patterns.
 - **ElectroDB:** The adapter uses ElectroDB to manage interactions with DynamoDB, providing a layer of abstraction and type safety over raw DynamoDB operations.
@@ -266,7 +266,7 @@ This storage adapter utilizes a **single-table design pattern** with [ElectroDB]
 Key aspects of this approach:
 
 - **DynamoDB Native:** The single-table design is optimized for DynamoDB's key-value and query capabilities, often leading to better performance and capacity compared to mimicking relational models.
-- **External Table Management:** Unlike some adapters that might offer helper functions to create tables via code, this adapter **expects the DynamoDB table and its associated Global Secondary Indexes (GSIs) to be provisioned externally** before use. Please refer to [TABLE\_SETUP.md](https://github.com/mastra-ai/mastra/blob/main/stores/dynamodb/TABLE_SETUP.md) for detailed instructions using tools like AWS CloudFormation or CDK. The adapter focuses solely on interacting with the pre-existing table structure.
+- **External Table Management:** Unlike some adapters that might offer helper functions to create tables via code, this adapter **expects the DynamoDB table and its associated Global Secondary Indexes (GSIs) to be provisioned externally** before use. Please refer to [TABLE_SETUP.md](https://github.com/mastra-ai/mastra/blob/main/stores/dynamodb/TABLE_SETUP.md) for detailed instructions using tools like AWS CloudFormation or CDK. The adapter focuses solely on interacting with the pre-existing table structure.
 - **Consistency via Interface:** While the underlying storage model differs, this adapter adheres to the same `MastraStorage` interface as other adapters, ensuring it can be used interchangeably within the Mastra `Memory` component.
 
 ### Mastra Data in the Single Table

package/dist/docs/references/integrations-databases-postgresql.md

@@ -429,14 +429,14 @@ PostgreSQL storage provides index management to optimize query performance.
 PostgreSQL storage creates composite indexes during initialization for common query patterns:
 
 - `mastra_threads_resourceid_createdat_idx`: (resourceId, createdAt DESC)
-- `mastra_messages_thread_id_createdat_idx`: (thread\_id, createdAt DESC)
+- `mastra_messages_thread_id_createdat_idx`: (thread_id, createdAt DESC)
 - `mastra_ai_spans_traceid_startedat_idx`: (traceId, startedAt DESC)
 - `mastra_ai_spans_parentspanid_startedat_idx`: (parentSpanId, startedAt DESC)
 - `mastra_ai_spans_name_startedat_idx`: (name, startedAt DESC)
 - `mastra_ai_spans_scope_startedat_idx`: (scope, startedAt DESC)
 - `mastra_scores_trace_id_span_id_created_at_idx`: (traceId, spanId, createdAt DESC)
-- `mastra_workflow_snapshot_name_createdat_idx`: (workflow\_name, createdAt DESC)
-- `mastra_workflow_snapshot_name_status_createdat_idx`: (workflow\_name, snapshot->>'status', createdAt DESC), created only when the `snapshot` column is `jsonb`
+- `mastra_workflow_snapshot_name_createdat_idx`: (workflow_name, createdAt DESC)
+- `mastra_workflow_snapshot_name_status_createdat_idx`: (workflow_name, snapshot->>'status', createdAt DESC), created only when the `snapshot` column is `jsonb`
 
 These indexes improve performance for filtered queries with sorting, including `dateRange` filters on message queries and Studio's workflow runs-list.
 
@@ -485,7 +485,7 @@ For advanced index types, you can specify additional options:
 
 **name** (`string`): Unique name for the index
 
-**table** (`string`): Table name (e.g., 'mastra\_threads')
+**table** (`string`): Table name (e.g., 'mastra_threads')
 
 **columns** (`string[]`): Array of column names with optional sort order (e.g., \['id', 'createdAt DESC'])
 

package/dist/docs/references/reference-memory-memory-class.md

@@ -37,11 +37,11 @@ export const agent = new Agent({
 
 **embedder** (`EmbeddingModel<string> | EmbeddingModelV2<string>`): Embedder instance for vector embeddings. Required when semantic recall is enabled.
 
-**embeddingDimension** (`number`): Output dimension of the embedder, as a positive integer. When set, Memory uses it to name the semantic recall index instead of embedding a probe string on first use. It must match the vectors the embedder returns: a mismatch throws a MASTRA\_MEMORY\_EMBEDDING\_DIMENSION\_MISMATCH error before any index is created. See Setting the embedding dimension.
+**embeddingDimension** (`number`): Output dimension of the embedder, as a positive integer. When set, Memory uses it to name the semantic recall index instead of embedding a probe string on first use. It must match the vectors the embedder returns: a mismatch throws a MASTRA_MEMORY_EMBEDDING_DIMENSION_MISMATCH error before any index is created. See Setting the embedding dimension.
 
 **options** (`MemoryConfig`): Memory configuration options.
 
-**options.lastMessages** (`number | false`): Number of most recent messages to include in context. Set to false to disable the message history feature entirely (messages are not loaded into context or saved). Use Number.MAX\_SAFE\_INTEGER to retrieve all messages with no limit. To load messages without saving new ones, use the readOnly option. The window slides forward on every request, so once a thread exceeds the limit, each turn invalidates the provider prompt cache. For long-running conversations, use Observational Memory instead.
+**options.lastMessages** (`number | false`): Number of most recent messages to include in context. Set to false to disable the message history feature entirely (messages are not loaded into context or saved). Use Number.MAX_SAFE_INTEGER to retrieve all messages with no limit. To load messages without saving new ones, use the readOnly option. The window slides forward on every request, so once a thread exceeds the limit, each turn invalidates the provider prompt cache. For long-running conversations, use Observational Memory instead.
 
 **options.messageHistory** (`{ maxTokens: number; atMaxRemoveTokens?: number }`): Token budget for the complete prompt, including remembered history, system instructions, context, and the current turn. When the prompt exceeds maxTokens, the oldest remembered messages are dropped until the prompt is at most maxTokens - atMaxRemoveTokens (defaults to 25% of maxTokens). Protected content is never removed. Linked tool calls and results are removed together. During agent runs, trimmed history is excluded from later turns via a persisted per-thread boundary, but the messages themselves stay in storage. When set without an explicit lastMessages, the default 10-message cap is not applied. Set maxTokens to 0 to disable message history. Prefer this over lastMessages, since message count is a poor proxy for context size.
 

package/dist/docs/references/reference-rag-chunking-and-embedding.md

@@ -118,7 +118,7 @@ const { embeddings } = await embedMany({
 })
 ```
 
-Google (text-embedding-001):
+Google (gemini-embedding-001):
 
 ```ts
 const { embeddings } = await embedMany({

package/dist/docs/references/reference-rag-retrieval.md

@@ -382,6 +382,7 @@ Vector store prompts define query patterns and filtering capabilities for each v
 
 ```ts
 import { MONGODB_PROMPT } from '@mastra/mongodb'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -416,6 +417,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { PINECONE_PROMPT } from '@mastra/pinecone'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -433,6 +435,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { QDRANT_PROMPT } from '@mastra/qdrant'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -450,6 +453,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { CHROMA_PROMPT } from '@mastra/chroma'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -467,6 +471,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { ASTRA_PROMPT } from '@mastra/astra'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -484,6 +489,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { LIBSQL_PROMPT } from '@mastra/libsql'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -501,6 +507,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { UPSTASH_PROMPT } from '@mastra/upstash'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -518,6 +525,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { VECTORIZE_PROMPT } from '@mastra/vectorize'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -535,6 +543,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { OPENSEARCH_PROMPT } from '@mastra/opensearch'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -552,6 +561,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { ORACLEDB_PROMPT } from '@mastra/oracledb'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',
@@ -569,6 +579,7 @@ export const ragAgent = new Agent({
 
 ```ts
 import { S3VECTORS_PROMPT } from '@mastra/s3vectors'
+import { Agent } from '@mastra/core/agent'
 
 export const ragAgent = new Agent({
   id: 'rag-agent',

package/dist/docs/references/reference-storage-retention.md

@@ -294,7 +294,7 @@ const storage = new MongoDBStore({
 
 ## Reclaiming disk
 
-`prune()` deletes rows but doesn't shrink the database file. On SQLite/libSQL the freed pages go on a freelist and are reused by future writes, so the file stops growing: for most users this alone solves the unbounded-growth problem.
+`prune()` deletes rows but doesn't shrink the database file. On SQLite/libSQL the freed pages go on a freelist for reuse by future writes. Reusing these pages prevents unbounded file growth for most users.
 
 Handing that free space back to the OS is a separate concern that Mastra doesn't manage. If you specifically need to shrink the file, run the underlying database's compaction (for example `VACUUM` on self-hosted libSQL) yourself in a maintenance window. A full `VACUUM` locks the file and needs roughly twice the file size in free disk. On PostgreSQL, autovacuum reclaims dead tuples for reuse automatically. A manual `VACUUM FULL` is only needed if you must return disk to the OS.
 

package/dist/docs/references/reference-tools-vector-query-tool.md

@@ -436,6 +436,7 @@ For multi-tenant applications where each tenant has isolated data (e.g., separat
 ```typescript
 import { createVectorQueryTool, VectorStoreResolver } from '@mastra/rag'
 import { PgVector } from '@mastra/pg'
+import { RequestContext } from '@mastra/core/request-context'
 
 // Cache for tenant-specific vector stores
 const vectorStoreCache = new Map<string, PgVector>()

package/dist/docs/references/reference-vectors-pg.md

@@ -30,7 +30,7 @@ The PgVector class provides vector search using [PostgreSQL](https://www.postgre
 
 **pgPoolOptions** (`PoolConfig`): Additional pg pool configuration options
 
-**disableInit** (`boolean`): When true, automatic DDL (schema, extension, table, and index creation) inside createIndex is skipped. Useful for CI/CD pipelines where schema and indexes are managed separately and the runtime database role lacks DDL privileges. Can also be enabled with the MASTRA\_DISABLE\_STORAGE\_INIT environment variable. (Default: `false`)
+**disableInit** (`boolean`): When true, automatic DDL (schema, extension, table, and index creation) inside createIndex is skipped. Useful for CI/CD pipelines where schema and indexes are managed separately and the runtime database role lacks DDL privileges. Can also be enabled with the MASTRA_DISABLE_STORAGE_INIT environment variable. (Default: `false`)
 
 ## Constructor examples