pg_stat_progress_copy.tuples_skipped

Description

Number of tuples skipped because they contain malformed data. This counter only advances when a value other than stop is specified to the ON_ERROR option.

View

pg_stat_progress_copy

Field

tuples_skipped

SQL type

bigint

Units named in the field definition

tuples

Reset observation

No stats_reset field is documented for this view

Usage

SELECT tuples_skipped FROM pg_catalog.pg_stat_progress_copy;

View semantics

Whenever COPY is running, the pg_stat_progress_copy view will contain one row for each backend that is currently running a COPY command. The table below describes the information that will be reported and provides information about how to interpret it.

Collection and reset context

Read the same-version statistics collection and view documentation below for reset scope and visibility. No per-field reset rule is inferred from the field name.

Inspect this field

Example query; no execution result or measured value is asserted.

SELECT tuples_skipped FROM pg_catalog.pg_stat_progress_copy;

Related entries

• pg_stat_progress_copy columns
• Statistics collection and reset functions

Documentation and source

• PostgreSQL 18 English manual

Compare versions

PostgreSQL 16 → 17: added.

--- PostgreSQL 16
+++ PostgreSQL 17
@@ -1 +1,8 @@
-Not recorded in this version
+{
+  "field": "tuples_skipped",
+  "sql_type": "bigint",
+  "units_mentioned": [
+    "tuples"
+  ],
+  "view": "pg_stat_progress_copy"
+}

Compares recorded interfaces and attributes. Source fingerprints and build metadata are excluded; an absent sample is not proof of the introduction or removal release.

Related entries

• pg_stat_progress_copy.bytes_processed
• pg_stat_progress_copy.bytes_total
• pg_stat_progress_copy.command
• pg_stat_progress_copy.datid
• pg_stat_progress_copy.datname
• pg_stat_progress_copy.pid
• pg_stat_progress_copy.relid
• pg_stat_progress_copy.tuples_excluded
• pg_stat_progress_copy.tuples_processed
• pg_stat_progress_copy.type