Skip to content
Written with Claude
IMPORTANT

As you may notice, this page and pretty much the entire website were obviously created with the help of AI. I wonder how you could tell? Was it a big "Written With Claude" badge on every page? I moved it to the top now (with the help of AI of course) to make it even more obvious. There are a few blogposts that were written by me manually, the old-fashioned way, I hope there will be more in the future, and those have a similar "Human Written" badge. This project (not the website), on the other hand, is a very, very different story. It took me more than two years of painstaking and unpaid work in my own free time. A story that, hopefully, I will tell someday. But meanwhile, what would you like me to do? To create a complex documentation website with a bunch of highly technical articles with the help of AI and fake it, to give you an illusion that I also did that manually? Like the half of itnernet is doing at this point? How does that makes any sense? Is that even fair to you? Or maybe to create this website manually, the old-fashioned way, just for you? While working a paid job for a salary, most of you wouldn't even get up in the morning. Would you like me to sing you a song while we're at it? For your personal entertainment? Seriously, get a grip. Do you find this information less valuable because of the way this website was created? I give my best to fix it to keep the information as accurate as possible, and I think it is very accurate at this point. If you find some mistakes, inaccurancies or problems, there is a comment section at the bottom of every page, which I also made with the help of the AI. And I woould very much appreciate if you leave your feedback there. Look, I'm just a guy who likes SQL, that's all. If you don't approve of how this website was constructed and the use of AI tools, I suggest closing this page and never wever coming back. And good riddance. And I would ban your access if I could know how. Thank you for your attention to this matter.

COMMAND_TIMEOUT

Also known as

timeout (with or without @ prefix)

Set the query execution timeout for the endpoint.

Syntax

@timeout <interval>
@command_timeout <interval>

Or using custom parameter syntax:

@timeout = <interval>
@command_timeout = <interval>

The value uses the interval format. Common examples:

UnitExamples
Microseconds1000us, 1000usec, 1000microseconds
Milliseconds500ms, 500msec, 500milliseconds
Seconds30, 30s, 30sec, 30seconds
Minutes5m, 5min, 5minutes
Hours1h, 1hour, 1hours
Days1d, 1day, 1days
Weeks1w, 1week, 1weeks

Single Token Requirement

The @timeout annotation reads only the first token after the keyword. Use formats without spaces to avoid parsing issues. Numbers without a unit default to seconds.

Default Value

The default timeout is configured via NpgsqlRest.CommandTimeout in configuration. If not set, defaults to 30 seconds.

Examples

Short Timeout

sql
create function quick_lookup(_id int)
returns json
language sql
as $$select row_to_json(t) from table t where id = _id$$;

comment on function quick_lookup(int) is
'HTTP GET
@timeout 5s';

Long Running Query

sql
create function generate_report(_year int)
returns json
language sql
as $$...complex aggregation...$$;

comment on function generate_report(int) is
'HTTP GET
@timeout 2min
@authorize';

Using Seconds Format

sql
comment on function slow_process() is
'HTTP POST
@command_timeout 90s';

Behavior

  • Overrides the global NpgsqlRest.CommandTimeout configuration for this endpoint.
  • Query is cancelled if it exceeds the timeout.
  • On timeout, returns the response configured in ErrorHandlingOptions.TimeoutErrorMapping.

Timeout Response

When a command times out, the response is determined by the TimeoutErrorMapping configuration:

json
{
  "ErrorHandlingOptions": {
    "TimeoutErrorMapping": {
      "StatusCode": 504,
      "Title": "Command execution timed out",
      "Details": null,
      "Type": null
    }
  }
}

Default timeout response: HTTP 504 Gateway Timeout

See Error Handling for customizing timeout responses.

Comments

Released under the MIT License.