Jelte Fennema-Nio
Jelte Fennema-Nio
> Any cloud provider that updates to 1.21.0 will instantly break all Prisma Client application that use pgbouncer=true To be clear, that should be "any cloud provider deploys 1.21.0 and...
Took a quick look at this. My understanding is that this combines two things into one PR: 1. Removing support for Postgres 9.6 (which seems reasonable to me) 2. Supporting...
Thanks for the work on this! I also had something like this in mind, but I was thinking about using FOREIGN TABLES instead of table access methods for this. So...
Thinking about it more, I do think FOREIGN TABLE is a better fit for this semantically. Because the CREATE TABLE command that you have now isn't actually creating the backing...
I tried reproducing this issue myself, but I was unable to. Does this still reproduce for you?
I have good hope that this has been fixed by #877. So closing this. If you can still reproduce, please reopen (or open a new issue).
It seems Alpine is getting this same issue now too. We should probably go and fix this soonish, my guess is that it has something to do with the OpenSSL...
applicationname_add_host originally had the purpose of still being able to show the IP of the client in postgres logs when PgBouncer and the client are on different nodes. The usage...
Closing this, since there was no response for a long time.
Thanks a lot for the contribution, but I'm starting to think that we should simply not support this until duckdb itself actually has support for this command.