3 Commits (0f77a2d028414a616da37d0a07813dfaf61e5d5f)

Author	SHA1	Message	Date
Jack Christensen	832b4f9771	Fix: prepared statement already exists ... When a conn is going to execute a query, the first thing it does is to deallocate any invalidated prepared statements from the statement cache. However, the statements were removed from the cache regardless of whether the deallocation succeeded. This would cause subsequent calls of the same SQL to fail with "prepared statement already exists" error. This problem is easy to trigger by running a query with a context that is already canceled. This commit changes the deallocate invalidated cached statements logic so that the statements are only removed from the cache if the deallocation was successful on the server. https://github.com/jackc/pgx/issues/1847	2024-02-03 12:33:17 -06:00
Jack Christensen	7de53a958b	stmtcache: Use deterministic, stable statement names ... Statement names are now a function of the SQL. This may make database diagnostics, monitoring, and profiling easier.	2023-09-23 09:55:05 -05:00
Jack Christensen	e7aa76ccf9	SendBatch now uses pipeline mode to prepare and describe statements ... Previously, a batch with 10 unique parameterized statements executed 100 times would entail 11 network round trips. 1 for each prepare / describe and 1 for executing them all. Now pipeline mode is used to prepare / describe all statements in a single network round trip. So it would only take 2 round trips.	2022-07-09 09:32:36 -05:00