Timeouts not applied correctly against Neon database

[egoldschmidt]

Setting idle_in_transaction_session_timeout, statement_timeout, and lock_timeout via pg pool config does not appear to work against Neon databases.

Screenshot 1 - params set locally against Postgres 16 in Docker container:

Screenshot 2 - params set against Neon, both direct & pgbouncer:

My methodology is simply to run await pool.query('SHOW lock_timeout');

Note that in screenshot 2 the lock timeout is zero. If I explicitly run SET lock_timeout = ... it works fine.

[charmander]

Do you have any reason to suspect this isn’t a bug/omission in Neon, or a misconfiguration of Neon? That’d be my guess.

Anyway, does it happen with libpq-based clients, like psql?

$ psql 'options=-c\ lock_timeout=12345'
=> SHOW lock_timeout;
 lock_timeout 
--------------
 12345ms

[egoldschmidt]

Fair point, likely a Neon issue indeed but figured I'd post here for broader visibility in case this kind of issue cropped up for others in the future, perhaps with other Postgres-compatible databases. (The thought that these parameters could be ignored blew my mind).

I just remembered that Neon is open source too so filed here: neondatabase/neon#12856

[charmander]

Have you had a chance to check psql?