Just to let you know... the issue still persists on 1.2.2.

@RiskyMH @Jarred-Sumner @cirospaciari

Just to let you know... the issue still persists on 1.2.2.

@RiskyMH @Jarred-Sumner @cirospaciari

Can you send a repro?
Im trying the following code:

import { Elysia } from "elysia";
import { SQL } from "bun";

const sql = new SQL({
  url: "postgresql://bun:bunbunbun@localhost:5432/bun",
  idleTimeout: 5,
});

new Elysia({ serve: { idleTimeout: 10 } })
  .get("/", async () => {
    const res = await sql`SELECT * FROM "users" limit 1`;
    return { rows: res };
  })
  .listen(3000, () => {
    console.log("Server is running on port 3000");
  });
await fetch("http://localhost:3000/")
  .then(res => res.json())
  .then(console.log);

await Bun.sleep(10_000);
await fetch("http://localhost:3000/")
  .then(res => res.json())
  .then(console.log);

Output using bun --revision 1.2.2+c1708ea6a:

Output using bunx [email protected] test.mjs or bunx [email protected] test.mjs

Just one file... using the simple code:

import { Elysia } from 'elysia'
import { SQL } from 'bun'
// import postgres from 'postgres'

const sql = new SQL({ url: process.env.DATABASE_URL, max: 10, idleTimeout: 5 });

// const sql = postgres(process.env.DATABASE_URL, { max: 10, idle_timeout: 5});


new Elysia({ serve: { idleTimeout: 10 } })
    .get('/', async () => {
        const res = await sql`SELECT * FROM cidades`;
        return { rows: res };
    })
    .listen(3000, () => {
        console.log('Server is running on port 3000');
    });

I just tested on Linux as well... same result.

Here is a new video showing the case.

https://youtu.be/m8YBA96rlPY

And I dont know if is important or not... but, the reuslt set is kind a big...

And, another information that I belive may be relevant... using K6, before, I use to get alot of timeouts... now, I get none... but, if I send the request slowly like in the video.... the problem happens.

@belizariogr running on Windows, Linux or MacOS I cannot reproduce this when using neon.tech or localhost databases even if I return 100k users, what service are you using for the database? Wondering if is some IPV6/IPV4 problem

Im running this also in localhost.

Im running this also in localhost.

You are using Postgres 17 right? maybe this is the problem Im testing with 14, 15 and 16 will try with 17 tomorrow will reopen the Issue and investigate further

And, if was a IPv6/v4 problem of some sort... the problem should be happing on the posgres driver as well.

Yes... Postgres 17.

can confirm, with lots of data Bun.sql times out but postgres.sql works

Yes... Postgres 17.

Ok got the repro will work on this tomorrow, Thank you @belizariogr

Just tested on Postgres 16... and have the same result... but, limiting the results on 1 record... no issues... The problem is related with large result set.... apparently.

Testing here... the problem only happens when the result set is more than 100 KB.... If is less than that... no issues.

Testing here... the problem only happens when the result set is more than 100 KB.... If is less than that... no issues.

this makes sense as even if you increase timeout to something huge, it never actually finishes.