GOMODULES
/
pgx
mirror of https://github.com/jackc/pgx.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
3,574 Commits
61 Branches
101 Tags
7.9 MiB
Commit Graph

3574 Commits (d38dd857565046d05fb5d1ef73d50364f36e388b)

Author SHA1 Message Date
robford d38dd85756 Allowed nxtf to signal end of data by returning nil,nil 
Added some test
Improved documentation
 2023-11-11 10:06:58 -06:00
robford 9b6d3809d6 added tests 2023-11-11 10:06:58 -06:00
robford b4d72d4fce copyFromFunc 2023-11-11 10:06:58 -06:00
robford ccdd85a5eb added ChopyFromCh 2023-11-11 10:06:58 -06:00
Jack Christensen 96f5f9cd95 Release v5.5.0 2023-11-04 10:27:32 -05:00
Kirill Mironov d3fb6e00da implement json.Marshaler and json.Unmarshaler for Float4, Float8 2023-11-04 10:25:31 -05:00
Jack Christensen cf6ef75f91 stdlib: Use Ping instead of CheckConn in ResetSession 
CheckConn is deprecated. It doesn't detect all network outages. It
causes a 1ms delay while it tries to read the connection. Ping incurs a
round trip but that means it is a much stronger guarantee that the
connection is usable. In addition, if the application and the database
are on the same network it will actually be faster as round trip times
are typically a few hundred microseconds.
 2023-10-26 20:41:44 -05:00
Jack Christensen 7a4bb7edb5
Add link to pgx presentation to README.md 2023-10-20 18:49:41 -05:00
Ivan Posazhennikov 6f7400f428 fix typo in the comment in the pgconn.go 2023-10-14 18:02:35 -05:00
Anton Levakin 304697de36 CancelRequest: Wait for the cancel request to be acknowledged by the server 2023-10-14 17:48:16 -05:00
Anton Levakin 5d0f904831 update TestConnContextCanceledCancelsRunningQueryOnServer 
Check cancellation of the request for pgbouncer
 2023-10-14 17:48:16 -05:00
Anton Levakin 6ca3d8ed4e Revert "CancelRequest: don't try to read the reply" 
This reverts commit c861bce438.
 2023-10-14 17:48:16 -05:00
Jack Christensen 81ddcfdefb Fix spurious deadline exceeded error 
stdlib_test.TestConnConcurrency had been flickering on CI deadline /
timeout errors. This was extremely confusing because the test deadline
was set for 2 minutes and the errors would occur much quicker.

The problem only manifested in an extremely specific and timing
sensitive situation.

1. The watchdog timer for deadlocked writes starts the goroutine to
   start the background reader
2. The background reader is stopped
3. The next operation is a read without a preceding write (AFAIK only
   CheckConn does this)
4. The deadline is set to interrupt the read
5. The goroutine from 1 actually starts the background reader
6. The background reader gets an error reading the connection with the
   deadline
7. The deadline is cleared
8. The next read on the connection will get the timeout error
 2023-10-14 11:38:33 -05:00
Jack Christensen 45f807fdb4 Special case the underlying type of []byte 
Underlying types were already tried. But []byte is not a normal
underlying type. It is a slice. But since is can be treated as a scalar
instead of an array / slice we need to special case it.

https://github.com/jackc/pgx/issues/1763
 2023-10-12 20:52:49 -05:00
Jack Christensen 8a09979417 Skip test on CockroachDB 2023-10-10 22:07:06 -05:00
Jack Christensen 7a2b93323c Prevent prematurely closing statements in database/sql 
This error was introduced by 0f0d236599.
If the same statement was prepared multiple times then whenever Close
was called on one of the statements the underlying prepared statement
would be closed even if other statements were still using it.

https://github.com/jackc/pgx/issues/1754#issuecomment-1752004634
 2023-10-10 21:56:26 -05:00
Nicola Murino 1484fec57f CI: add PostgreSQL 16 2023-10-10 20:54:54 -05:00
Nicola Murino 3957163808 Update supported Go versions and add 1.21 to CI 2023-10-10 20:54:54 -05:00
Jack Christensen 7fc908a5f2 Do not call t.Fatal in goroutine 
require.Equal internally calls t.Fatal, which is not safe to call in a
goroutine.
 2023-10-07 10:37:24 -05:00
Jack Christensen 0f0d236599 database/sql prepared statement names are deterministically generated 
stdlib now uses the functionality introduced in
bbe2653bc5 for prepared statements. This
means that the prepared statement name is stable for a given query even
across connections and program executions.

It also makes tracing easier.

See https://github.com/jackc/pgx/issues/1754
 2023-10-07 10:16:25 -05:00
Ville Skyttä c6c50110db Spelling and grammar fixes 2023-10-07 09:26:23 -05:00
Jack Christensen 91530db629 Fix typo in string.Cut refactor 2023-10-07 09:20:28 -05:00
Ville Skyttä 24ed0e4257 Make use of strings.Cut 2023-10-04 20:41:55 +03:00
Jack Christensen 163eb68866 Normalize timeout error when receiving pipeline results 
https://github.com/jackc/pgx/issues/1748#issuecomment-1740437138
 2023-09-30 08:50:40 -05:00
Jack Christensen a61517a83b SendBatch should pass ctx to StartPipeline 
https://github.com/jackc/pgx/issues/1748
 2023-09-28 20:00:02 -05:00
Vincent Le Goff d93f31b8fa docs: GetPoolConnector 2023-09-25 08:51:12 -05:00
Jack Christensen cf72a00f52 Skip test of unsupported operation on CockroachDB 2023-09-23 10:49:11 -05:00
Jack Christensen c08cc72306 Improve QueryExecModeCacheDescribe and clarify documentation 
QueryExecModeCacheDescribe actually is safe even when the schema or
search_path is modified. It may return an error on the first execution
but it should never silently encode or decode a value incorrectly. Add a
test to demonstrate and ensure this behavior.

Update documentation of QueryExecModeCacheDescribe to remove warning of
undetected result decoding errors.

Update documentation of QueryExecModeCacheStatement and
QueryExecModeCacheDescribe to indicate that the first execution of an
invalidated statement may fail.
 2023-09-23 10:35:42 -05: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 bbe2653bc5 Prepare chooses statement name based on sql if name == sql 
This makes it easier to explicitly manage prepared statements.

refs #1716
 2023-09-23 08:40:06 -05:00
Mochammad Hanif R 4e7aa59d64 Fix typos in docs 2023-09-23 07:20:36 -05:00
Lev Zakharov b301530a5f add doc for OpenDBFromPool 2023-09-09 08:13:56 -05:00
Lev Zakharov f42824cab3 update docs 2023-09-09 08:13:56 -05:00
Lev Zakharov 18856482c4 remove before/after acquire hooks 2023-09-09 08:13:56 -05:00
Lev Zakharov 639691c0ab add test for stdlib.OpenDBFromPool 2023-09-09 08:13:56 -05:00
Lev Zakharov 3e716c4b06 add example to the doc 2023-09-09 08:13:56 -05:00
Lev Zakharov 51ade172e5 refactor to use the same connection implementation 2023-09-09 08:13:56 -05:00
Lev Zakharov 3d4540aa1b add *sql.DB construction from *pgxpool.Pool 2023-09-09 08:13:56 -05:00
Julien GOTTELAND 389931396e No data result on error 2023-08-19 18:31:41 -05:00
Julien GOTTELAND 9ee7d29cf9 Add CollectExactlyOneRow function 2023-08-19 18:31:41 -05:00
Craig Ringer a7375cc503 docs: Emphasise need to call rows.Err() after rows.Next() returns false 
The Rows interface in pgx, like its ancestor in database/sql, is easy to
accidentally misuse in a way that can cause apps to misinterpret
database or connection errors as successful queries with empty or
truncated result-sets.

Update the docs to emphasise the need to call rows.Err() after
rows.Next() returns false, and direct users of the interface to the v5
API helpers that make writing correct code easier.

The docs on Conn.Query() already call this out, so only a small change
is needed to warn users and point them at the details on Query()

Per details in #1707
 2023-08-10 17:19:15 -05:00
Jack Christensen d43bd349c1 Add batch insert benchmarks 2023-08-08 18:44:31 -05:00
Jack Christensen 5c6cf62b53 Fix off by one error in benchmark 2023-08-08 18:38:34 -05:00
Jack Christensen d17440d5c7 Add missed changelog entry and fix typo 2023-08-05 08:36:48 -05:00
Jack Christensen 4c60839c48 Release v5.4.3 2023-08-05 08:24:37 -05:00
Jack Christensen e9087eacb8 Fix data race when pgproto3 trace is enabled during CopyFrom 
https://github.com/jackc/pgx/issues/1703
 2023-08-05 07:30:59 -05:00
Jack Christensen d626dfe94e TestConnConcurrency has been failing on CI 
This probably won't fix it, but at the very least we should not be
running assertions in a goroutine.
 2023-07-28 18:13:31 -05:00
Jack Christensen 1a9b2a53a5 Fix staticcheck issues 2023-07-28 18:04:31 -05:00
Alexey Palazhchenko 8fb309c631 Use Go 1.20's link syntax for `ParseConfig` 2023-07-28 17:51:42 -05:00
horpto f4533dc906 optimize parseNumericString 2023-07-25 19:25:23 -05:00