Fix native pipelining: guard handleError when query.native is unset and skip JS-only tests

handleError in native/query.js crashes when this.native is undefined
(e.g. query_timeout fires before pipeline callback sets it).

Skip named statement cleanup and query_timeout tests for native client
since those features rely on JS-specific internals.

Author: mcollina

packages/pg/lib/native/query.js

@@ -48,7 +48,7 @@ const errorFieldMap = {
 
 NativeQuery.prototype.handleError = function (err) {
   // copy pq error fields into the error object
-  const fields = this.native.pq.resultErrorFields()
+  const fields = this.native && this.native.pq.resultErrorFields()
   if (fields) {
     for (const key in fields) {
       const normalizedFieldName = errorFieldMap[key] || key

packages/pg/test/integration/client/pipelining-tests.js

@@ -105,48 +105,58 @@ suite.test('end() waits for in-flight pipelined queries to complete', async func
 })
 
 // #13: named statement error cleanup — submittedNamedStatements not left stale
-suite.test('named statement parse error cleans up and allows re-preparation', async function () {
-  const client = helper.client()
-  client.pipelining = true
-
-  // Use an invalid type to force a server-side parse error
-  const err = await client
-    .query({ name: 'bad-stmt', text: 'SELECT $1::nonexistent_type_xyz', values: [1] })
-    .then(() => null)
-    .catch((e) => e)
-
-  assert.ok(err, 'expected parse to fail')
-
-  // The stale submittedNamedStatements entry should be gone.
-  // Re-using the same name with valid SQL should work.
-  const result = await client.query({ name: 'bad-stmt', text: 'SELECT $1::int AS n', values: [42] })
-  assert.equal(result.rows[0].n, 42)
-
-  await client.end()
-})
+// This relies on submittedNamedStatements tracking which only exists in the JS client
+suite.test(
+  'named statement parse error cleans up and allows re-preparation',
+  !helper.args.native &&
+    async function () {
+      const client = helper.client()
+      client.pipelining = true
+
+      // Use an invalid type to force a server-side parse error
+      const err = await client
+        .query({ name: 'bad-stmt', text: 'SELECT $1::nonexistent_type_xyz', values: [1] })
+        .then(() => null)
+        .catch((e) => e)
+
+      assert.ok(err, 'expected parse to fail')
+
+      // The stale submittedNamedStatements entry should be gone.
+      // Re-using the same name with valid SQL should work.
+      const result = await client.query({ name: 'bad-stmt', text: 'SELECT $1::int AS n', values: [42] })
+      assert.equal(result.rows[0].n, 42)
+
+      await client.end()
+    }
+)
 
 // #14: query_timeout with pipelining
 // When an already-sent pipelined query times out, the connection is destroyed
 // to unblock the pipeline — subsequent queries error rather than hanging.
-suite.test('query_timeout on sent pipelined query destroys connection to unblock', async function () {
-  const client = helper.client()
-  client.pipelining = true
-  client.on('error', () => {}) // absorb the 'error' event emitted when stream is destroyed
-
-  const results = await Promise.allSettled([
-    client.query('SELECT 1 AS num'),
-    client.query({ text: 'SELECT pg_sleep(30)', query_timeout: 100 }),
-    client.query('SELECT 3 AS num'),
-  ])
-
-  // Query 1 completes before the slow query enters the pipeline
-  assert.equal(results[0].status, 'fulfilled')
-  assert.equal(results[0].value.rows[0].num, 1)
-
-  // Query 2 times out
-  assert.equal(results[1].status, 'rejected')
-  assert.ok(results[1].reason.message.includes('timeout'), `unexpected error: ${results[1].reason.message}`)
-
-  // Query 3 errors because the connection was destroyed to unblock the pipeline
-  assert.equal(results[2].status, 'rejected')
-})
+// Native client does not support query_timeout in pipelining mode.
+suite.test(
+  'query_timeout on sent pipelined query destroys connection to unblock',
+  !helper.args.native &&
+    async function () {
+      const client = helper.client()
+      client.pipelining = true
+      client.on('error', () => {}) // absorb the 'error' event emitted when stream is destroyed
+
+      const results = await Promise.allSettled([
+        client.query('SELECT 1 AS num'),
+        client.query({ text: 'SELECT pg_sleep(30)', query_timeout: 100 }),
+        client.query('SELECT 3 AS num'),
+      ])
+
+      // Query 1 completes before the slow query enters the pipeline
+      assert.equal(results[0].status, 'fulfilled')
+      assert.equal(results[0].value.rows[0].num, 1)
+
+      // Query 2 times out
+      assert.equal(results[1].status, 'rejected')
+      assert.ok(results[1].reason.message.includes('timeout'), `unexpected error: ${results[1].reason.message}`)
+
+      // Query 3 errors because the connection was destroyed to unblock the pipeline
+      assert.equal(results[2].status, 'rejected')
+    }
+)