fix: update PostgresKVStore constructor params

[gorango]

Allow initializing with pg client or pool instance

[changeset-bot]

🦋 Changeset detected

Latest commit: 507c3ec

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 11 packages

Name	Type
llamaindex	Patch
docs	Patch
@llamaindex/autotool	Patch
@llamaindex/experimental	Patch
@llamaindex/cloudflare-worker-agent-test	Patch
@llamaindex/next-agent-test	Patch
@llamaindex/nextjs-edge-runtime-test	Patch
@llamaindex/next-node-runtime-test	Patch
@llamaindex/waku-query-engine-test	Patch
@llamaindex/autotool-01-node-example	Patch
@llamaindex/autotool-02-next-example	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
llama-index-ts-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 23, 2024 5:48pm

[pkg-pr-new]

Open in Stackblitz

@llamaindex/autotool

pnpm add https://pkg.pr.new/run-llama/LlamaIndexTS/@llamaindex/autotool@1240

@llamaindex/cloud

pnpm add https://pkg.pr.new/run-llama/LlamaIndexTS/@llamaindex/cloud@1240

@llamaindex/community

pnpm add https://pkg.pr.new/run-llama/LlamaIndexTS/@llamaindex/community@1240

@llamaindex/core

pnpm add https://pkg.pr.new/run-llama/LlamaIndexTS/@llamaindex/core@1240

@llamaindex/env

pnpm add https://pkg.pr.new/run-llama/LlamaIndexTS/@llamaindex/env@1240

@llamaindex/experimental

pnpm add https://pkg.pr.new/run-llama/LlamaIndexTS/@llamaindex/experimental@1240

llamaindex

pnpm add https://pkg.pr.new/run-llama/LlamaIndexTS/llamaindex@1240

@llamaindex/wasm-tools

pnpm add https://pkg.pr.new/run-llama/LlamaIndexTS/@llamaindex/wasm-tools@1240

commit: 507c3ec

[gorango]

I also I updated the docStore.utils methods for docToJson and jsonToDoc to allow skipping the calls to parse & stringify when handling doc data in the PostgresDocumentStore since Postgres can store and retrieve raw JSON

[himself65]

I like this PR but I will consider the usage of nativeJson here

[gorango]

I have reverted the JSON changes as they are not directly related to this PR.

I opened a separate PR for the JSON bit. My rationale is:

• storing the raw JSON allows querying in pg and
• there are performance benefits in avoiding the additional steps involved in parse/stringify especially with large objects.