Skip to content
deedglassdocs

row_limit_exceeded

A postgres.execute statement changed more rows than the connector’s maxrowsaffected (1,000 by default).

HTTP 400 · invalid_request_error · not retryable

What happened

Section titled “What happened”

A postgres.execute statement changed more rows than the connector’s max_rows_affected (1,000 by default). Deedglass rolled the transaction back, so neither the change nor the ledger row was committed, and the action is failed.

What to do

Section titled “What to do”

Narrow the WHERE clause, or raise max_rows_affected in the connector’s config if the size is expected.

Example

Section titled “Example”
HTTP 400 · row_limit_exceeded
{
  "error": {
    "type": "invalid_request_error",
    "code": "row_limit_exceeded",
    "message": "The statement changed 1,204 rows, over this connector's limit of 1,000. Nothing was committed. Narrow the WHERE clause.",
    "param": null,
    "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d",
    "doc_url": "https://docs.deedglass.com/errors/row_limit_exceeded"
  }
}

The message is for a person and can get more exact over time: branch on type and code, never on the message.

In the SDKs

Section titled “In the SDKs”
SDK Raised as
TypeScript (@deedglass/sdk) InvalidRequestError with code === "row_limit_exceeded"
Python (deedglass) deedglass.InvalidRequestError with .code == "row_limit_exceeded"
Section titled “Related”