Jack Christensen
Jack Christensen
pgx just sends the query to PostgreSQL. If you can do it in psql you should be able to do it in pgx.
I'm not sure that baking custom fallback handling directly into pgx/pgxpool is a good idea. However, I would be more open to adding features that make it more convenient for...
As you say, detecting broken TCP connections is non-trivial. I wonder if a write timeout would even work reliably? As I understand it, from Go's point of view, the write...
I'm open to some new setting for a write timeout. Not sure exactly what the interface would be though. Not sure how directly setting SetWriteDeadline would interact with the existing...
See #2185. I proposed something there that might have some overlap with this.
I'm not sure I understand. Are you actually expecting multiple result sets from a single PostgreSQL query or is some library just expecting the interface to be implemented? For the...
v4 is not getting any changes except bug fixes.
Yes, it would be reasonable for v5.
This might be possible, but it also could be difficult and a significant change. A notice could be received at any time. Not just while receiving query results. In addition,...
@rf Given that the same problem occurs in pgx and in pq, it makes me doubt the problem is in pgx. Is a load balancer or connection pooler being used?...