From 859d344d52ad94c08a05846aec75afdacd376997 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 4 Aug 2026 17:30:56 +0000 Subject: [PATCH] automatic update of reference docs for spicedb --- app/spicedb/concepts/commands/page.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/app/spicedb/concepts/commands/page.mdx b/app/spicedb/concepts/commands/page.mdx index 3efc6bd7..62656496 100644 --- a/app/spicedb/concepts/commands/page.mdx +++ b/app/spicedb/concepts/commands/page.mdx @@ -92,9 +92,9 @@ spicedb datastore gc [flags] --datastore-engine string type of datastore to initialize ("cockroachdb", "mysql", "postgres", "spanner") (default "memory") --datastore-experimental-column-optimization enable experimental column optimization (default true) --datastore-follower-read-delay-duration duration amount of time to subtract from non-sync revision timestamps to ensure they are sufficiently in the past to enable follower reads (CockroachDB and Spanner drivers only) or read replicas (Postgres and MySQL drivers only) (default 4.8s) - --datastore-gc-interval duration amount of time between passes of garbage collection (Postgres driver only) (default 3m0s) - --datastore-gc-max-operation-time duration maximum amount of time a garbage collection pass can operate before timing out (Postgres driver only) (default 1m0s) - --datastore-gc-window duration amount of time before revisions are garbage collected (default 24h0m0s) + --datastore-gc-interval duration how often the background worker deletes data that has aged out of the gc window; affects disk usage only, never which revisions are readable (Postgres and MySQL only) (default 3m0s) + --datastore-gc-max-operation-time duration maximum amount of time a garbage collection pass can operate before timing out (Postgres and MySQL only) (default 1m0s) + --datastore-gc-window duration how far into the past clients may read: revisions older than this are rejected as stale, regardless of whether their data has been physically deleted yet (default 24h0m0s) --datastore-include-query-parameters-in-traces include query parameters in traces (Postgres and CockroachDB drivers only) --datastore-max-tx-retries int number of times a retriable transaction should be retried (default 10) --datastore-migration-phase string datastore-specific flag that should be used to signal to a datastore which phase of a multi-step migration it is in @@ -237,9 +237,9 @@ spicedb datastore repair [flags] --datastore-engine string type of datastore to initialize ("cockroachdb", "mysql", "postgres", "spanner") (default "memory") --datastore-experimental-column-optimization enable experimental column optimization (default true) --datastore-follower-read-delay-duration duration amount of time to subtract from non-sync revision timestamps to ensure they are sufficiently in the past to enable follower reads (CockroachDB and Spanner drivers only) or read replicas (Postgres and MySQL drivers only) (default 4.8s) - --datastore-gc-interval duration amount of time between passes of garbage collection (Postgres driver only) (default 3m0s) - --datastore-gc-max-operation-time duration maximum amount of time a garbage collection pass can operate before timing out (Postgres driver only) (default 1m0s) - --datastore-gc-window duration amount of time before revisions are garbage collected (default 24h0m0s) + --datastore-gc-interval duration how often the background worker deletes data that has aged out of the gc window; affects disk usage only, never which revisions are readable (Postgres and MySQL only) (default 3m0s) + --datastore-gc-max-operation-time duration maximum amount of time a garbage collection pass can operate before timing out (Postgres and MySQL only) (default 1m0s) + --datastore-gc-window duration how far into the past clients may read: revisions older than this are rejected as stale, regardless of whether their data has been physically deleted yet (default 24h0m0s) --datastore-include-query-parameters-in-traces include query parameters in traces (Postgres and CockroachDB drivers only) --datastore-max-tx-retries int number of times a retriable transaction should be retried (default 10) --datastore-migration-phase string datastore-specific flag that should be used to signal to a datastore which phase of a multi-step migration it is in @@ -415,9 +415,9 @@ spicedb serve [flags] --datastore-engine string type of datastore to initialize ("cockroachdb", "mysql", "postgres", "spanner") (default "memory") --datastore-experimental-column-optimization enable experimental column optimization (default true) --datastore-follower-read-delay-duration duration amount of time to subtract from non-sync revision timestamps to ensure they are sufficiently in the past to enable follower reads (CockroachDB and Spanner drivers only) or read replicas (Postgres and MySQL drivers only) (default 4.8s) - --datastore-gc-interval duration amount of time between passes of garbage collection (Postgres driver only) (default 3m0s) - --datastore-gc-max-operation-time duration maximum amount of time a garbage collection pass can operate before timing out (Postgres driver only) (default 1m0s) - --datastore-gc-window duration amount of time before revisions are garbage collected (default 24h0m0s) + --datastore-gc-interval duration how often the background worker deletes data that has aged out of the gc window; affects disk usage only, never which revisions are readable (Postgres and MySQL only) (default 3m0s) + --datastore-gc-max-operation-time duration maximum amount of time a garbage collection pass can operate before timing out (Postgres and MySQL only) (default 1m0s) + --datastore-gc-window duration how far into the past clients may read: revisions older than this are rejected as stale, regardless of whether their data has been physically deleted yet (default 24h0m0s) --datastore-include-query-parameters-in-traces include query parameters in traces (Postgres and CockroachDB drivers only) --datastore-max-tx-retries int number of times a retriable transaction should be retried (default 10) --datastore-migration-phase string datastore-specific flag that should be used to signal to a datastore which phase of a multi-step migration it is in