You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be a pretty easy fix if you're interested in doing a PR. Otherwise I'll get to it soon-ish but I've got a bunch of other stuff in the pipeline too. 🙏
error: unsupported startup parameter: statement_timeout
at Connection.parseE (/Users/gajus/Documents/dev/rayroute/rayman/node_modules/pg/lib/connection.js:614:13)
at Connection.parseMessage (/Users/gajus/Documents/dev/rayroute/rayman/node_modules/pg/lib/connection.js:413:19)
at TLSSocket.<anonymous> (/Users/gajus/Documents/dev/rayroute/rayman/node_modules/pg/lib/connection.js:129:22)
at TLSSocket.emit (events.js:321:20)
at TLSSocket.EventEmitter.emit (domain.js:485:12)
at addChunk (_stream_readable.js:297:12)
at readableAddChunk (_stream_readable.js:273:9)
at TLSSocket.Readable.push (_stream_readable.js:214:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:186:23)
At @loomhq we are looking to see if we can using this with our sequelize setup. I noticed statement_timeout doesn't get applied when using the native driver as well. Proposed a PR to fix in #2323. Also, added support for idle_in_transaction_session_timeout.
This is expected from pgbouncer, because statement_timeout is not part of ignore_startup_parameters (pgbouncer's config). However, when the fix ships it will complain on options (since we do options=-c statement_timeout=...).
The issue here is pgbouncer ignores startup parameter once added to ignore_startup_parameters (it only does so that pgbouncer doesn't hard fail), so passing statement_timeout via options to pgbouncer won't work I believe.
The fix should still work when working against DB server.
I use slonik which uses node-postgres under the hood and have to connect to PgBouncer. I keep getting "unsupported startup parameter" error and I have no clue PgBouncer is incompatible with these timeout options. Disabling them fixed it.
Activity
test: skip a test failing because of node-postgres bug. @see brianc/n…
brianc commentedon Feb 12, 2020
This might be a pretty easy fix if you're interested in doing a PR. Otherwise I'll get to it soon-ish but I've got a bunch of other stuff in the pipeline too. 🙏
gajus commentedon Feb 13, 2020
Switching to the JavaScript driver now throws:
boromisp commentedon May 21, 2020
@gajus Could the
unsupported startup parametererror be related to this: https://www.pgbouncer.org/config.html#ignore_startup_parameters?shayonj commentedon Aug 30, 2020
At @loomhq we are looking to see if we can using this with our sequelize setup. I noticed
statement_timeoutdoesn't get applied when using the native driver as well. Proposed a PR to fix in #2323. Also, added support foridle_in_transaction_session_timeout.shayonj commentedon Sep 3, 2020
Re:
This is expected from pgbouncer, because
statement_timeoutis not part ofignore_startup_parameters(pgbouncer's config). However, when the fix ships it will complain onoptions(since we dooptions=-c statement_timeout=...).The issue here is pgbouncer ignores startup parameter once added to
ignore_startup_parameters(it only does so that pgbouncer doesn't hard fail), so passingstatement_timeoutviaoptionstopgbouncerwon't work I believe.The fix should still work when working against DB server.
lemuelflores commentedon Jul 11, 2023
@shayonj Thanks. I appreciate the explanation.
I use slonik which uses
node-postgresunder the hood and have to connect to PgBouncer. I keep getting "unsupported startup parameter" error and I have no clue PgBouncer is incompatible with these timeout options. Disabling them fixed it.test: skip a test failing because of node-postgres bug. @see brianc/n…