ruvector/crates/ruvector-postgres/docker
rUv ee40332ce1 fix(postgres): Resolve compilation errors and Docker build issues
- Fix simsimd Option/Result type mismatch in scaled_dot.rs
- Fix f32/f64 type conversions in poincare.rs and lorentz.rs
- Fix AVX512 missing wrapper functions by using AVX2 fallback
- Fix Vec<Vec<f32>> to JsonB for pgrx pg_extern compatibility
- Fix DashMap get() to get_mut() for mutable access
- Fix router.rs dereference for best_score comparison
- Update Dockerfile to copy pre-written SQL file for pgrx
- Simplify init.sql to use correct function names
- Add postgres-cli npm package for CLI tooling

All changes tested successfully in Docker with:
- Extension loads with AVX2 SIMD support (8 floats/op)
- Distance functions verified working
- PostgreSQL 16 container runs successfully

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-12-03 01:17:50 +00:00
..
dev.sh feat(postgres): Add 7 advanced AI modules to ruvector-postgres 2025-12-02 20:12:48 +00:00
docker-compose.yml feat(postgres): Add 7 advanced AI modules to ruvector-postgres 2025-12-02 20:12:48 +00:00
Dockerfile fix(postgres): Resolve compilation errors and Docker build issues 2025-12-03 01:17:50 +00:00
Dockerfile.test feat(postgres): Add 7 advanced AI modules to ruvector-postgres 2025-12-02 20:12:48 +00:00
init.sql fix(postgres): Resolve compilation errors and Docker build issues 2025-12-03 01:17:50 +00:00
README.md feat(postgres): Add 7 advanced AI modules to ruvector-postgres 2025-12-02 20:12:48 +00:00
run-tests.sh feat(postgres): Add 7 advanced AI modules to ruvector-postgres 2025-12-02 20:12:48 +00:00

RuVector-Postgres Docker Infrastructure

Docker-based development and testing environment for the ruvector-postgres PostgreSQL extension.

Quick Start

Development Environment

# Start development environment
./dev.sh start

# Open psql shell
./dev.sh psql

# Watch for changes and auto-reload
./dev.sh watch

# Stop environment
./dev.sh stop

Running Tests

# Run full test suite
./run-tests.sh

# Run integration tests only
./run-tests.sh --integration

# Keep container running for debugging
./run-tests.sh --keep-running

# Clean rebuild
./run-tests.sh --clean

Scripts Overview

dev.sh - Development Environment

Manages a PostgreSQL development environment with hot-reload support.

Commands:

  • start - Start development environment (default)
  • stop - Stop development environment
  • restart - Restart development environment
  • logs - Show PostgreSQL logs
  • psql - Open psql shell
  • watch - Start file watcher for hot-reload (requires cargo-watch)
  • rebuild - Rebuild and reload extension
  • status - Show container status

Options:

  • -p, --port PORT - PostgreSQL port (default: 5432)
  • -u, --user USER - PostgreSQL user (default: postgres)
  • -d, --database DB - PostgreSQL database (default: ruvector_dev)
  • -f, --foreground - Start in foreground with logs
  • -h, --help - Show help message

Examples:

# Start on custom port
./dev.sh --port 5433 start

# View logs
./dev.sh logs

# Rebuild extension
./dev.sh rebuild

run-tests.sh - Test Runner

Builds Docker image, runs tests, and manages test infrastructure.

Options:

  • -b, --build-only - Build Docker image only, don't run tests
  • -t, --test-only - Run tests only (skip build)
  • -i, --integration - Run integration tests only
  • -k, --keep-running - Keep container running after tests
  • -c, --clean - Clean up before starting
  • -v, --keep-volumes - Keep volumes after cleanup
  • -p, --port PORT - PostgreSQL port (default: 5433)
  • -h, --help - Show help message

Examples:

# Build and test
./run-tests.sh

# Integration tests with container kept running
./run-tests.sh --integration --keep-running

# Clean rebuild
./run-tests.sh --clean --build-only

Docker Files

Dockerfile - Main Build File

Multi-stage Docker build for PostgreSQL 16 with pgrx 0.12.6 support.

Features:

  • Rust 1.75 with Bookworm base
  • PostgreSQL 16 with development headers
  • cargo-pgrx 0.12.6 pre-installed
  • Optimized layer caching for dependencies
  • Health checks built-in

docker-compose.yml - Orchestration

Complete development stack with PostgreSQL and pgAdmin.

Services:

  • postgres - PostgreSQL 16 with ruvector extension
  • pgadmin - Web-based database management (port 5050)

Usage:

# Start all services
docker-compose up -d

# View logs
docker-compose logs -f

# Stop services
docker-compose down

# Access pgAdmin
# URL: http://localhost:5050
# Email: admin@ruvector.dev
# Password: admin

init.sql - Database Initialization

SQL script for automatic database setup with:

  • Extension creation
  • Sample tables and indexes
  • Test data
  • Performance monitoring views

Development Workflow

1. Initial Setup

# Start development environment
./dev.sh start

# This will:
# - Pull PostgreSQL 16 image
# - Create development database
# - Expose on localhost:5432
# - Show connection string

2. Build Extension

cd /workspaces/ruvector/crates/ruvector-postgres

# Build and install extension
cargo pgrx install --release

3. Test Changes

# Quick test in psql
./dev.sh psql

# In psql:
# CREATE EXTENSION ruvector_postgres;
# SELECT '[1,2,3]'::vector;

4. Hot-Reload Development

# Install cargo-watch (one time)
cargo install cargo-watch

# Start watching for changes
./dev.sh watch

# Now edit code - extension auto-reloads on save!

5. Run Full Test Suite

# Run all tests
./run-tests.sh

# Or run just integration tests
./run-tests.sh --integration

Environment Variables

Development (dev.sh)

POSTGRES_PORT=5432          # PostgreSQL port
POSTGRES_USER=postgres      # PostgreSQL user
POSTGRES_PASSWORD=postgres  # PostgreSQL password
POSTGRES_DB=ruvector_dev    # Database name

Testing (run-tests.sh)

POSTGRES_PORT=5433          # PostgreSQL port (different from dev)
POSTGRES_USER=ruvector      # PostgreSQL user
POSTGRES_PASSWORD=ruvector  # PostgreSQL password
POSTGRES_DB=ruvector_test   # Test database name
KEEP_VOLUMES=false          # Keep volumes after cleanup
EXPORT_DB=false             # Export database dump

Platform Support

Both scripts support:

  • Linux (Ubuntu, Debian, RHEL, etc.)
  • macOS (Intel and Apple Silicon)
  • Windows (via WSL2)

The scripts automatically detect the platform and adjust behavior accordingly.

Troubleshooting

Port Already in Use

# Check what's using the port
lsof -i :5432

# Use a different port
./dev.sh --port 5433 start

Extension Not Loading

# Rebuild extension
./dev.sh rebuild

# Or manually:
cd /workspaces/ruvector/crates/ruvector-postgres
cargo pgrx install --release

# Then reload in database
./dev.sh psql
# DROP EXTENSION ruvector_postgres CASCADE;
# CREATE EXTENSION ruvector_postgres;

Docker Build Fails

# Clean build
docker system prune -a
./run-tests.sh --clean --build-only

# Check Docker resources
docker info

Tests Fail

# Keep container running to debug
./run-tests.sh --keep-running

# Connect to inspect
./dev.sh psql

# View logs
docker logs ruvector-postgres-test

Performance Tips

Build Optimization

# Use BuildKit for faster builds
export DOCKER_BUILDKIT=1
./run-tests.sh

# Parallel builds
docker build --build-arg MAKEFLAGS="-j$(nproc)" ...

Development Speed

# Use cargo-watch for instant feedback
./dev.sh watch

# Or use cargo-pgrx run for interactive development
cd /workspaces/ruvector/crates/ruvector-postgres
cargo pgrx run pg16

CI/CD Integration

GitHub Actions Example

name: Test RuVector-Postgres

on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Run tests
        run: |
          cd crates/ruvector-postgres/docker
          ./run-tests.sh

GitLab CI Example

test:
  image: docker:latest
  services:
    - docker:dind
  script:
    - cd crates/ruvector-postgres/docker
    - ./run-tests.sh

Resources

License

MIT License - See project root for details