↑↓ select↵ open⌫ change scopeOpen full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

Wiki / SQLSTATE

HV010 — fdw_function_sequence_error

HV010 indicates that an FDW function was called in an invalid sequence. The fixed 18.6 core/contrib call scan has no resolved HV010 report group, so it does not establish a native callback or message.

English manual coverage begins with PostgreSQL 8.1. Source history and runtime observations have their own recorded version boundaries.

Reading PG 18·Select a recorded version

aliases
Unknown
class name
Foreign Data Wrapper Error (SQL/MED)
condition name
fdw_function_sequence_error
lang
en
sqlstate
HV010

Definition PG 18

HV010 — fdw_function_sequence_error

At a glance {#at-a-glance}

HV010 indicates that an FDW function was called in an invalid sequence. The fixed 18.6 core/contrib call scan has no resolved HV010 report group, so it does not establish a native callback or message.

Meaning {#meaning}

The condition is about the order or lifecycle of wrapper operations. fdwapi.h defines callback entry points such as planning and foreign-scan callbacks, but that API background does not emit HV010 or define every wrapper's legal sequence.

Messages and diagnostics {#messages}

No resolved 18.6 core/contrib message variant was found. Keep the complete message, callback name, operation phase, wrapper/driver version, and whether the call followed planning, scan start, iteration, rescan, modification, or cleanup.

Diagnosis {#diagnosis}

Trace the wrapper's state machine around the failing callback. Verify which object was initialized, whether the callback was repeated or skipped, and whether cleanup ran before a later call. Use the wrapper's own contract and source mapping to decide whether the reported sequence is local or remote.

Response {#response}

Restore the sequence required by the installed wrapper and its callback contract, then validate the same operation from a fresh object state. Avoid repeating a callback blindly: a wrapper may have already issued a remote request or released its state.

Versions {#versions}

HV010 is present in the locked definition snapshots from 9.1.24 through 18.6 and 19 Beta 3, with known_present_by 9.1.0. The available pre-9 definition material does not prove an exact introduction release.

Related {#related}

HV00B concerns an invalid handle; HV00K concerns a reply handle; HV009 concerns invalid null-pointer use.

Sources {#sources}

  • errcodes.txt — definition, SHA-256 6e8de346643ba84aa3c9c6a73360acfc7b2dfb89162c06c08ce9bf5bcd5bbcba.
  • fdwapi.h — generic FDW callback boundary.
  • Structured evidence — fixed 18.6 sources and bounded scan.

Compare versions

SQLSTATE evidence and recorded runtime versions

claims · identity
{
  "claim_id": "identity",
  "limits": "",
  "method": "Read the fixed errcodes definition row and macro.",
  "position": 0,
  "runtime": [],
  "sources": [
    "src.errcodes.18.6"
  ],
  "statement": "HV010 is fdw_function_sequence_error in SQL/MED Class HV."
}
claims · api-boundary
{
  "claim_id": "api-boundary",
  "limits": "Generic API context is background only and does not prove an emitting path for this SQLSTATE.",
  "method": "Read the fixed FDW callback signatures and FdwRoutine structure.",
  "position": 1,
  "runtime": [],
  "sources": [
    "src.fdwapi.18.6"
  ],
  "statement": "The condition name identifies an FDW function-sequence state. The generic callback API provides phase boundaries only; it does not establish a source path that emits HV010."
}
claims · scan-boundary
{
  "claim_id": "scan-boundary",
  "limits": "This scan does not cover external wrappers, drivers, remote systems, or user callbacks; absence from the scan is not an absolute absence claim.",
  "method": "Compare resolved report groups with the fixed macro mapping.",
  "position": 2,
  "runtime": [],
  "sources": [
    "src.calls.REL_18_6",
    "src.errcodes.18.6"
  ],
  "statement": "No resolved HV010 report group was found in the locked PostgreSQL 18.6 core/contrib call scan."
}
claims · history-boundary
{
  "claim_id": "history-boundary",
  "limits": "Definition presence does not prove runtime use.",
  "method": "Compare the canonical release-definition facts with the available pre-9 source boundary.",
  "position": 3,
  "runtime": [],
  "sources": [
    "src.errcodes.18.6"
  ],
  "statement": "The locked release definition snapshots establish presence from the known 9.1.0 boundary; the available pre-9 material does not establish an exact introduction release."
}
sources · src.errcodes.18.6
{
  "commit": "724edf9bde9d356724ad384a2e196edc3c9f80f7",
  "docs_url": "",
  "kind": "upstream_source",
  "location": "",
  "path": "src/backend/utils/errcodes.txt",
  "position": 0,
  "sha256": "6e8de346643ba84aa3c9c6a73360acfc7b2dfb89162c06c08ce9bf5bcd5bbcba",
  "source_id": "src.errcodes.18.6",
  "tag": "REL_18_6",
  "url": "https://github.com/postgres/postgres/blob/724edf9bde9d356724ad384a2e196edc3c9f80f7/src/backend/utils/errcodes.txt"
}
sources · src.fdwapi.18.6
{
  "commit": "724edf9bde9d356724ad384a2e196edc3c9f80f7",
  "docs_url": "",
  "kind": "upstream_source",
  "location": "",
  "path": "src/include/foreign/fdwapi.h",
  "position": 1,
  "sha256": "572ba892e6435ca92d3b3bc84dde5bbd3160cc3a082693daab8daa835c4d2cd7",
  "source_id": "src.fdwapi.18.6",
  "tag": "REL_18_6",
  "url": "https://github.com/postgres/postgres/blob/724edf9bde9d356724ad384a2e196edc3c9f80f7/src/include/foreign/fdwapi.h"
}
sources · src.calls.REL_18_6
{
  "commit": "",
  "docs_url": "",
  "kind": "local_artifact",
  "location": "",
  "path": "raw/calls/REL_18_6.jsonl",
  "position": 2,
  "sha256": "9ee8a0e81d8f0825c5c1ae45583439859a26e602bdd4ce2f2a62aa278867ccbf",
  "source_id": "src.calls.REL_18_6",
  "tag": "",
  "url": ""
}

Source references

Full definition and evidence JSON

Definition sources

center · PostgreSQL 18 · english-manuals:906fc25c3d2a7618d96ed93fde0a1ee4fd843846d7dba1006d144e626fcc7975

Text language: en · english-manuals:906fc25c3d2a7618d96ed93fde0a1ee4fd843846d7dba1006d144e626fcc7975