Jelte Fennema-Nio
Jelte Fennema-Nio
According to this stack overflow answer it can mean lots of different things being wrong: https://stackoverflow.com/a/43849220/2570866 Maybe datastudio.google and PgBouncer have different ciphers configured.
Hi @dpirotte, github notified me that you rebased this on a branch of your fork. I think a rebased version of this can be merged pretty easily. Could you still...
> Moreover, replication connections cannot be reliably reused at all. Thanks. I updated the wording in the PR to include that.
I fixed all the things I wanted to in this PR. So I think it's ready for a more thorough review now.
> Ops... I realized that you did it. Another suggestion is to explain in the commit message that it is a requirement for this feature. I added a commit message...
That does seem like a bug indeed. Feel free to create a PR to fix it. As a workaround you should be able to put the actual password in the...
Yeah this is a known issue, that is tracked here: https://github.com/pgbouncer/pgbouncer/issues/452 I responded to that one just now with the current state of possible workarounds.
Yes, this is a problem. This should be fixed in a libusual its cfparser: https://github.com/libusual/libusual/blob/master/usual/cfparser.c Feel free to provide a PR on that repo.
Which client are you using? It would be good to list a disclaimer in the docs that prepared statements don't work for them, just as for PDO.
Closing this as I updated the docs to say that PDO does not work with prepared statements currently.