Database Setup
Configure PostgreSQL, connection pooling, backups, and migrations.
Last updated March 15, 2026
Open VTS uses PostgreSQL as its primary database. This guide covers production database configuration, connection pooling, and backup strategies.
Database Configuration
conf/openvts.xml
<entry key="database.driver">org.postgresql.Driver</entry>
<entry key="database.url">jdbc:postgresql://localhost:5432/openvts</entry>
<entry key="database.user">openvts</entry>
<entry key="database.password">your_secure_password</entry>
<entry key="database.maximumPoolSize">10</entry>PostgreSQL Optimization
Apply these PostgreSQL settings for optimal Open VTS performance:
postgresql.conf
# Memory
shared_buffers = 2GB # 25% of available RAM
effective_cache_size = 6GB # 75% of available RAM
work_mem = 64MB
# Write-ahead log
wal_buffers = 64MB
checkpoint_completion_target = 0.9
# Query planning
random_page_cost = 1.1 # SSD-optimized
effective_io_concurrency = 200Backup Strategy
backup.sh
#!/bin/bash
# Daily automated backup
DATE=$(date +%Y%m%d_%H%M)
pg_dump -U openvts -Fc openvts > /backups/openvts_$DATE.dump
# Keep last 30 days
find /backups -name "openvts_*.dump" -mtime +30 -deleteDanger
Always test your backup restoration process before going to production. Use
pg_restore to verify backup integrity regularly.