LTRIM

Removes elements from both ends a list. Deletes the list if all elements were trimmed.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	LTRIM
Catalog group	List commands
Upstream since	1.0.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

LTRIM key start stop

ffkv behavior and limits

A successful pop removes the item immediately: Redis list queues have no acknowledgement or automatic redelivery. Blocking calls do not wait in EXEC or Lua. Only large list/native-job bodies are SSD-offloaded in hybrid mode.

Source: README.md:155–174, 810–825; tests/bdd/features/lists.feature.

All requests share the 8 MiB framing/1,024-argument ingress limit; normal RESP replies have 64 MiB wire/logical budgets with bounded nesting/value counts. Management and Lua origins impose smaller budgets. These are not a process RSS cap. Catalog inclusion is not exhaustive option or wire-format parity. See limits and compatibility.

Upstream metadata

The following fields come from the pinned Redis metadata, not measured ffkv performance or an assertion that ffkv enforces every upstream flag. Running COMMAND INFO/COMMAND DOCS describe the current engine.

Upstream Redis complexity: O(N) where N is the number of elements to be removed by the operation.

Upstream arity: 4 (includes the command name; a negative number is a minimum).

Command flags: WRITE.

ACL categories: LIST.

Argument structure

Argument	Type	Constraints / metadata
key	key	key_spec_index: 0
start	integer	Required
stop	integer	Required

Key specifications

Upstream key discovery descriptors (indexes are relative to the full command vector):

[
  {
    "flags": [
      "RW",
      "DELETE"
    ],
    "begin_search": {
      "index": {
        "pos": 1
      }
    },
    "find_keys": {
      "range": {
        "lastkey": 0,
        "step": 1,
        "limit": 0
      }
    }
  }
]

Additional pinned upstream metadata

{
  "group": "list",
  "since": "1.0.0"
}

Metadata source · Local snapshot: src/command_metadata.json, key ltrim.

BDD coverage and source examples

These are source observations, not a test run performed by this documentation build. A tag identifies scenario intent; an extracted vector identifies a command invocation, which may intentionally produce an error. Scenarios may require setup, multiple connections, persistence, cluster nodes or native-module fixtures.

• Negative indexes and inclusive trim endpoints preserve list order — tests/bdd/features/lists.feature:163; command tag and invocation observed.
• Legacy right-to-left move rotates a same-key list and preserves its expiry — tests/bdd/features/lists.feature:450; invocation observed.
• List commands reject incompatible source values without replacing them (Scenario Outline) — tests/bdd/features/lists.feature:1047; command tag and invocation observed.

Extracted command vectors

The following JSON arrays are the test harness’s argument vectors, not shell commands. Numeric arguments are converted by the harness; objects of the form {"base64":"…"} represent decoded binary bytes, not a literal JSON command argument. Preserve scenario setup and connection ordering. See the CLI guide for shell quoting and binary stdin. No reply is invented or inferred.

Negative indexes and inclusive trim endpoints preserve list order — tests/bdd/features/lists.feature:190 (I execute:)

[
  "LTRIM",
  "q",
  "1",
  "-2"
]

Next source assertion: the reply equals:

"OK"

Legacy right-to-left move rotates a same-key list and preserves its expiry — tests/bdd/features/lists.feature:480 (the following commands succeed:)

[
  "LTRIM",
  "q",
  "0",
  "0"
]

List commands reject incompatible source values without replacing them — tests/bdd/features/lists.feature:1053 (I execute:)

Expanded from an actual Examples row: command=["LTRIM","wrong","0","-1"].

[
  "LTRIM",
  "wrong",
  "0",
  "-1"
]

Next source assertion: the reply is an error with code “WRONGTYPE”