From 7d0e118c8f35d1ee124e10913c834afefabb94bb Mon Sep 17 00:00:00 2001 From: Tina Ha Date: Wed, 24 Jun 2026 14:42:41 -0400 Subject: [PATCH] Update apps/docs/content/guides/database/storing-large-values.mdx Co-authored-by: Chris Chinchilla --- apps/docs/content/guides/database/storing-large-values.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/content/guides/database/storing-large-values.mdx b/apps/docs/content/guides/database/storing-large-values.mdx index 3f45d209297..766549c6063 100644 --- a/apps/docs/content/guides/database/storing-large-values.mdx +++ b/apps/docs/content/guides/database/storing-large-values.mdx @@ -44,7 +44,7 @@ Use this as a decision framework, not a rule: | You need transactional consistency with the row | The payload is an artifact (a generated file, a raw response log) | | Row count is moderate | The table grows without limit (e.g. one row per request) | -For AI apps, a common split: keep small, frequently queried fields (status, token counts, a short summary, embeddings) in Postgres; offload the raw prompt/response/log to [Storage](/docs/guides/storage) and keep a path pointer. +For AI apps, a common split is to keep small, frequently queried fields (status, token counts, a short summary, embeddings) in Postgres and offload the raw prompt/response/log to [Storage](/docs/guides/storage) and keep a path pointer. ## Keeping large values in Postgres