Sehrope Sarkuni

The driver knows about the data type of the parameters but it does not include them in the "parse" request sent to the server with the command SQL. Only the...

> And somewhat related is why does it try to read all fields as strings, even when it's a binary blob: The PostgreSQL wire protocol has two modes for transferring...

It's the lambda environment freeze / thaw causing this issue. You can't use a long lived connection pool with a lambda as there is no guarantee that the lambda will...

I think that's possible as the docs say it could be frozen or bounced at any time: https://docs.aws.amazon.com/lambda/latest/dg/runtimes-context.html The last line also says not to assume you have connections open...

> In a load of 5000 requests (50 concurrent), I received 22 message: 'Client was closed and is not queryable', That sounds like a bug in your either the pool...

Oh yes that'd definitely break under load. The client's have an internal query command queue so concurrent usage of client kind of works until it doesn't (i.e. anything that requires...

@boromisp Oh dang you're right. Lamda only sends a single request at a time to an instance. @filipedeschamps Forget my idea of keeping it open it if it's concurrently being...

Can you share the code for the example? Also, what's the max_connections on the server?

I tried out various combinations of tasks / pool sizes and I'm not able to reproduce this issue. Here's the code I tried out: ```js const POOL_SIZE = 10; const...

Is there a question or issue? That check was added to the SASL code to provide the end user with a more informative error message rather than just failing due...