GI don't believe so for Supabase hosted, it is in a config file https://github.com/supabase/postgres/blob/develop/ansible/files/pgbouncer_config/pgbouncer.ini.j2 and don't think you could change that in a setting accessible by SQL.
GitHub
Unmodified Postgres with some useful plugins. Contribute to supabase/postgres development by creating an account on GitHub.
Jgot it. I'm trying to connect it to zapier but I can't figure out how
GYou can't set the port on the Zapier postgres settings?
JIt's so bizarre, it errors out when i try it and the support agent said that they only support port 5432 
JJI realize this is on them not y'all, just thought it was weird enough to share
GAs a sanity check does it connect thru 5432 with the same settings?
JYUP
GSounds like their support is correct then. Odd they make it an option.
JAbsolutely bonkers. I don't even think there is a technical hurdle here besides...appending it to a string? lol
JAppreciate the help/responsiveness regardless gary
GIt would be pretty hard to run with pgbouncer at the standard port as then everything else using it would break and have to be changed anyway, so even changing the port number on Supabase side would be problematic.
JI can imagine, I was mostly grasping for straws
Jbtw the "absolutely bonkers" was towards zapier not supporting arbitrary port numbers, not y'all
JUpdate: the issue is that zapier sends an
options paramJadding
options here did the trick. That input field is readonly on hosted supabase though so I had to take that out lol but it works great
JAny consequences to this that I'm not aware of?
GBeyond my knowledge of pgbouncer. You probably need to ask a new question though if you have concerns, as this thead won't get much focus now.
