Skip to content

Conversation

@zakvdm
Copy link

@zakvdm zakvdm commented Nov 11, 2025

  • Use @aws/aurora-dsql-node-postgres-connector to simplify connection pool creation.

  • Speed up initial data load by inserting in batches which results in fewer roundtrips. This required node-pg-format.

  • Simplified the migrate script a bit by removing the use of --> statement-breakpoint

  • Added Prettier config

  • Some dependency upgrades to remove some of the warnings

- Use `@aws/aurora-dsql-node-postgres-connector` to simplify connection
pool creation.

- Speed up initial data load by inserting in batches which results in
fewer roundtrips. This required node-pg-format.

- Simplified the migrate script a bit by removing the use of `--> statement-breakpoint`

- Added Prettier config

- Some dependency upgrades to remove some of the warnings
@vercel
Copy link

vercel bot commented Nov 11, 2025

@zakvdm is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​aws/​aurora-dsql-node-postgres-connector@​0.1.0721009984100
Addednode-pg-format@​1.3.5871009777100
Updateddrizzle-kit@​0.28.1 ⏵ 0.31.69910096 +199 +1100

View full report

const now = new Date();

if (pool && cachedToken && cachedToken.expiresAt > now) {
export async function getPool() {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For my understanding, are we generally leaning towards always having the agent use pools for creating a connection? Curious if it makes sense to leave the original method as a fallback or just provide more options if the agent runs into some error while trying to use a pooled connection.

pool = new Pool({
pool = new AuroraDSQLPool({
host: process.env.DB_CLUSTER_ENDPOINT!,
region: process.env.AWS_REGION || 'us-east-1',
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we determine to use us-east-1 value as the default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants