Sehrope Sarkuni

You're probably running your tests without the database password available to the test environment. If you're having an actual issue with this library then provide a self contained example that...

@Quintinius The "localhost" in that connection URI would connect over TCP, not a unix socket. Check your pg_hba to see if TCP connections are requiring SASL. It's probably only local...

You can use the pool but you need to check out the connection as the pool thinks the entire command is complete when the original query function returns. So use...

It ensures that all parts of your application use the same connection configuration and respect the same max pool size. If you need to change any of those things it...

It is a regular connection. But instead of doing: ```js const client = new pg.Client(/* config goes here */); await client.connect(); try { // do something with client } catch...

FYI, that last example of yours is creating a new *pool*, not a new *client*. The `pool.query(...)` internally uses `pool.connect(...)` to check out a connection, execute that one query, wait...

> Maybe the simplest solution is a pool of pools - associated array (an object with properties where each property name is a connection string, and property value is Pool...

This is confirmed to be a bug. Here's a (failing) test case to add to the repo to verify it: ``` // pgjdbc/src/test/java/org/postgresql/jdbc/ParameterTest.java /* * Copyright (c) 2024, PostgreSQL Global...

This package has not been updated in a considerable amount of time and has not been tested on recent node versions. I should update the README accordingly. If you're looking...

@minfrin You can enable actions to run on your pgjdbc fork as well. This is particularly useful if you want to try running something in CI without opening a PR...