メニュー
Start duckgres with DuckLake (S3-backed storage with PostgreSQL metadata) for local testing. Use when testing duckgres against DuckLake or reproducing Fivetran sync issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ducklake-test |
| description | Start duckgres with DuckLake (S3-backed storage with PostgreSQL metadata) for local testing. Use when testing duckgres against DuckLake or reproducing Fivetran sync issues. |
Start duckgres with DuckLake configuration:
Start dependencies (PostgreSQL metadata store + MinIO object storage):
docker-compose up -d
Kill any existing duckgres process:
pkill -f duckgres || true
Ensure config file exists at duckgres_local_test.yaml:
host: "0.0.0.0"
port: 35437
data_dir: "./data"
users:
postgres: "postgres"
extensions:
- ducklake
ducklake:
metadata_store: "postgres:host=localhost port=5433 user=ducklake password=ducklake dbname=ducklake"
object_store: "s3://ducklake/data/"
s3_provider: "config"
s3_endpoint: "localhost:9000"
s3_access_key: "minioadmin"
s3_secret_key: "minioadmin"
s3_region: "us-east-1"
s3_use_ssl: false
s3_url_style: "path"
Build and run duckgres:
go build -o duckgres . && ./duckgres --config duckgres_local_test.yaml
Connect with psql (in another terminal):
PGPASSWORD=postgres psql "host=127.0.0.1 port=35437 user=postgres sslmode=require"
To cleanup: pkill -f duckgres && docker-compose down
Tear down the multi-tenant K8s stack, kill port-forwards, and clean up worker pods. Use when done testing multi-tenant mode.
Build, deploy, and port-forward the multi-tenant control plane on local Kubernetes. Use when you need to test duckgres in multi-tenant mode with per-team worker pools.