Skip to content

HV007 — fdw_invalid_column_name

PostgreSQL SQLSTATE HV007 denotes an invalid column name passed through an FDW descriptor or callback. Check wrapper naming rules and quoting.

HV007 — fdw_invalid_column_name

At a glance

HV007 is an FDW-specific invalid-column-name condition. The 18.6 core/contrib scan found no direct report group, so the wrapper that validates the name and its message must be identified from the actual deployment.

Field Value
SQLSTATE HV007
Condition fdw_invalid_column_name
Status active
Known present by 9.1.0
Locked snapshots 9.1.24, 9.2.24, 9.3.25, 9.4.26, 9.5.25, 9.6.24, 10.23, 11.22, 12.22, 13.23, 14.24, 15.19, 16.15, 17.11, 18.6, 19beta3
Macros ERRCODE_FDW_INVALID_COLUMN_NAME
Aliases —

Meaning

The name reached the FDW API but violates the wrapper’s accepted descriptor or remote naming rules. That is different from HV005, where a name is valid in form but cannot be found, and from core 42703 on a local SQL query.

Messages and diagnostics

No fixed PostgreSQL core message is confirmed. Preserve the original quoted/unquoted name, case folding, foreign table, callback phase, and wrapper version.

Diagnosis

Inspect the wrapper’s name parser and remote identifier rules. Compare pg_attribute.attname, generated query identifiers, and any quoted or case-sensitive remote names. Locate the wrapper’s pinned source before assigning a repair to PostgreSQL itself.

Response

Use a name accepted by both the local foreign-table definition and the remote system, or configure the wrapper’s explicit name mapping. Rebuild the foreign descriptor after changing metadata; repeating the same statement is not useful.

Versions

HV007 is present from 9.1.0 through 18.6 and 19 Beta 3. The available pre-9 source definition scan did not observe this SQLSTATE.

HV005 is “column name not found”; HV008 is an invalid column number; 42703 is the local undefined-column code.

Sources