Some checks failed
go: build dev binaries / cleanup (push) Successful in 4s
Codespell / Check for spelling errors (push) Failing after 3s
docker: build dev containers / build-rust-binaries (amd64, x86_64-unknown-linux-musl) (push) Failing after 3s
docker: build dev containers / build-dev-containers (push) Has been skipped
docker: build dev containers / build-rust-binaries (arm64, true, aarch64-unknown-linux-musl) (push) Failing after 3s
End to End / FUSE Mount (push) Failing after 2s
EC Integration Tests / EC Integration Tests (push) Failing after 30s
FUSE DLM Integration Tests / FUSE DLM Integration Tests (push) Failing after 3s
FUSE Volume Server Failover Tests / FUSE Volume Server Failover (push) Failing after 3s
FUSE Integration Tests / FUSE Integration Testing (push) Failing after 2s
FUSE P2P Peer Chunk Sharing Integration Tests / FUSE P2P Peer Chunk Sharing (push) Failing after 3s
go: build binary / Go Vet (push) Failing after 2s
go: build binary / Go Vet 32-bit (push) Failing after 3s
go: build binary / Build (push) Failing after 4s
go: build binary / Build cross-platform (freebsd/amd64) (push) Failing after 3s
go: build binary / Build cross-platform (windows/amd64) (push) Failing after 3s
go: build binary / Build cross-platform (darwin/arm64) (push) Failing after 3s
go: build binary / Build cross-platform (windows/arm64) (push) Failing after 3s
go: build binary / Test (push) Failing after 2s
go: build binary / Test 32-bit (push) Failing after 3s
helm: lint and test charts / lint-test (push) Failing after 3s
Java Client Integration Tests / Java Integration Tests (11) (push) Failing after 3s
Java Client Integration Tests / Java Integration Tests (17) (push) Failing after 3s
go: build dev binaries / build_dev_linux_windows (amd64, linux) (push) Failing after 2s
go: build dev binaries / build_dev_linux_windows (amd64, windows) (push) Failing after 3s
go: build dev binaries / build_dev_darwin (amd64, darwin) (push) Has been skipped
go: build dev binaries / build_dev_darwin (arm64, darwin) (push) Has been skipped
Java Client Unit Tests / Java Unit Tests (11) (push) Failing after 3s
Java Client Unit Tests / Java Unit Tests (17) (push) Failing after 2s
Java Client Unit Tests / Java Unit Tests (21) (push) Failing after 3s
Java Client Unit Tests / Java Unit Tests (8) (push) Failing after 3s
Kafka Quick Test (Load Test with Schema Registry) / Kafka Client Load Test (Quick) (push) Failing after 3s
Kafka Gateway Tests / Kafka Unit Tests (unit-tests-1) (push) Failing after 11s
Kafka Gateway Tests / Kafka Integration Tests (Critical) (integration-1) (push) Failing after 3s
Kafka Gateway Tests / Kafka End-to-End Tests (with SMQ) (e2e-1) (push) Failing after 3s
Kafka Gateway Tests / Kafka Consumer Group Tests (Highly Isolated) (consumer-group-1) (push) Failing after 2s
Kafka Gateway Tests / Kafka Client Compatibility (with SMQ) (client-compat-1) (push) Failing after 3s
Kafka Gateway Tests / Kafka SMQ Integration Tests (Full Stack) (smq-integration-1) (push) Failing after 3s
Kafka Gateway Tests / Kafka Protocol Tests (Isolated) (protocol-1) (push) Failing after 3s
KMS Tests / KMS Provider Integration Tests (push) Failing after 2s
KMS Tests / S3 KMS End-to-End Tests (push) Failing after 3s
Master Cold Start Tests / Master Cold Start Tests (push) Failing after 4s
Metadata Subscribe Integration Tests / Metadata Subscribe Integration Tests (push) Failing after 3s
Multi-Master Tests / Multi-Master Failover Tests (push) Failing after 3s
Performance / CPU and Heap Profile (push) Failing after 2s
Performance / S3 Read/Write Benchmark (rust volume) (push) Failing after 3s
pjdfstest POSIX Compliance / pjdfstest (push) Failing after 2s
Plugin Worker Integration Tests / Plugin Worker: erasure_coding (push) Failing after 3s
Plugin Worker Integration Tests / Plugin Worker: vacuum (push) Failing after 3s
Rust Volume Server Tests / Rust Integration Tests (push) Failing after 3s
Rust Volume Server Tests / Go Tests with Rust Volume (grpc - Shard 1) (push) Failing after 2s
Rust Volume Server Tests / Go Tests with Rust Volume (http - Shard 1) (push) Failing after 3s
Rust Volume Server Tests / Go Tests with Rust Volume (grpc - Shard 2) (push) Failing after 3s
Rust Volume Server Tests / Go Tests with Rust Volume (http - Shard 2) (push) Failing after 3s
Rust Volume Server Tests / Go Tests with Rust Volume (grpc - Shard 3) (push) Failing after 3s
S3 IAM Integration Tests / S3 IAM Distributed Tests (push) Failing after 2s
S3 IAM Integration Tests / S3 IAM Performance Tests (push) Failing after 3s
Performance / Throughput Benchmark (go volume) (push) Failing after 3s
Performance / Throughput Benchmark (rust volume) (push) Failing after 2s
Performance / S3 Read/Write Benchmark (go volume) (push) Failing after 3s
Plugin Worker Integration Tests / Plugin Worker: volume_balance (push) Failing after 3s
PostgreSQL Gateway Tests / PostgreSQL Basic Tests (push) Failing after 3s
Rust Volume Server Tests / Rust Unit Tests (push) Failing after 2s
Rust Volume Server Tests / Go Tests with Rust Volume (http - Shard 3) (push) Failing after 3s
Rust Plugin Worker Tests / Rust Plugin Worker Build and Unit Tests (push) Failing after 3s
rust: build dev volume server binaries / cleanup (push) Successful in 3s
S3 ETag and ACL Tests / S3 ETag + ACL Integration Tests (push) Failing after 3s
S3 IAM Integration Tests / IAM Unit Tests (push) Failing after 3s
S3 IAM Integration Tests / S3 IAM Integration Tests (advanced) (push) Failing after 3s
S3 IAM Integration Tests / S3 IAM Integration Tests (basic) (push) Failing after 2s
S3 IAM Integration Tests / S3 IAM Integration Tests (group) (push) Failing after 3s
S3 IAM Integration Tests / S3 IAM Integration Tests (policy-enforcement) (push) Failing after 2s
S3 IAM Integration Tests / S3 IAM Integration Tests (sts) (push) Failing after 4s
S3 Keycloak Integration Tests / S3 Keycloak Integration Tests (push) Failing after 3s
S3 PyArrow Parquet Tests / PyArrow Parquet Tests (Python 3.11) (push) Failing after 3s
S3 PyArrow Parquet Tests / Go Unit Tests (Implicit Directory) (push) Has been cancelled
S3 PyArrow Parquet Tests / PyArrow Parquet Tests (Python 3.12) (push) Has been cancelled
rust: build dev volume server binaries / build-rust-volume-dev-darwin (darwin-amd64, x86_64-apple-darwin) (push) Has been cancelled
rust: build dev volume server binaries / build-rust-volume-dev-darwin (darwin-arm64, aarch64-apple-darwin) (push) Has been cancelled
rust: build dev volume server binaries / build-rust-volume-dev-linux (linux-amd64, x86_64-unknown-linux-gnu) (push) Has been cancelled
S3 PyArrow Parquet Tests / PyArrow Parquet Tests (Python 3.9) (push) Has been cancelled
S3 Proxy Signature Tests / S3 Proxy Signature Verification Tests (push) Has been cancelled
S3 SDK V2 Route Disambiguation Tests / S3 SDK V2 Routing Tests (push) Has been cancelled
S3 SSE Tests / S3 SSE Integration Tests (quick) (push) Has been cancelled
S3 SSE Tests / S3 SSE Compatibility Test (push) Has been cancelled
S3 SSE Tests / S3 SSE Metadata Persistence Test (push) Has been cancelled
S3 SSE Tests / S3 SSE Copy Operations Test (push) Has been cancelled
S3 SSE Tests / S3 SSE Multipart Upload Test (push) Has been cancelled
S3 SSE Tests / S3 SSE Performance Test (push) Has been cancelled
S3 SSE Tests / S3 Volume Encryption Test (push) Has been cancelled
S3 SSE Tests / S3 SSE Integration Tests (comprehensive) (push) Has been cancelled
Spark Integration Tests / Spark Integration Tests (push) Failing after 2s
Telemetry Integration Tests / telemetry-integration-test (push) Failing after 3s
Volume Server Integration Tests / Volume Server Integration Tests (grpc - Shard 1) (push) Failing after 3s
Volume Server Integration Tests / Volume Server Integration Tests (http - Shard 1) (push) Failing after 3s
Ceph S3 tests / Basic S3 tests (KV store) (push) Has been cancelled
Ceph S3 tests / S3 Versioning & Object Lock tests (push) Has been cancelled
S3 Policy Integration Tests / S3 Policy Unit Tests (push) Failing after 3s
Ceph S3 tests / S3 CORS tests (push) Has been cancelled
Ceph S3 tests / SeaweedFS Custom S3 Copy tests (push) Has been cancelled
Ceph S3 tests / Basic S3 tests (SQL store) (push) Has been cancelled
test s3 over https using aws-cli / awscli-tests (push) Has been cancelled
TLS Rotation Integration Tests / TLS Rotation Integration Tests (push) Has been cancelled
Vacuum Integration Tests / Vacuum Integration Tests (push) Has been cancelled
S3 Policy Integration Tests / S3 Policy Variables Integration Tests (push) Failing after 3s
S3 Policy Integration Tests / S3 Policy Enforcement Integration Tests (advanced-policy) (push) Failing after 3s
S3 Policy Integration Tests / S3 Policy Enforcement Integration Tests (basic-policy) (push) Failing after 2s
S3 Policy Integration Tests / S3 Policy Enforcement Integration Tests (contextual-policy) (push) Failing after 4s
S3 Policy Integration Tests / Trusted Proxy Detection Tests (push) Failing after 2s
S3 Policy Integration Tests / S3 Policy Shell Integration Tests (push) Failing after 3s
Samba on FUSE Integration / samba-integration (push) Failing after 2s
SFTP Integration Tests / SFTP Integration Testing (push) Failing after 3s
terraform: validate and test modules / fmt, validate, plan-level tests (push) Failing after 3s
terraform: validate and test modules / local cluster smoke test (real weed) (push) Failing after 2s
Volume Server Integration Tests / Volume Server Integration Tests (grpc - Shard 3) (push) Failing after 3s
Volume Server Integration Tests / Volume Server Integration Tests (grpc - Shard 2) (push) Failing after 3s
Volume Server Integration Tests / Volume Server Integration Tests (http - Shard 2) (push) Failing after 2s
Volume Server Integration Tests / Volume Server Integration Tests (http - Shard 3) (push) Failing after 5s
mount: windows conformance / WinFsp conformance (push) Has been cancelled
mount: windows / Mount on Windows (push) Has been cancelled
285 lines
8.7 KiB
Markdown
285 lines
8.7 KiB
Markdown
# PostgreSQL Wire Protocol Package
|
|
|
|
This package implements PostgreSQL wire protocol support for SeaweedFS, enabling universal compatibility with PostgreSQL clients, tools, and applications.
|
|
|
|
## Package Structure
|
|
|
|
```
|
|
weed/server/postgres/
|
|
├── README.md # This documentation
|
|
├── server.go # Main PostgreSQL server implementation
|
|
├── protocol.go # Wire protocol message handlers with MQ integration
|
|
├── DESIGN.md # Architecture and design documentation
|
|
└── IMPLEMENTATION.md # Complete implementation guide
|
|
```
|
|
|
|
## Core Components
|
|
|
|
### `server.go`
|
|
- **PostgreSQLServer**: Main server structure with connection management
|
|
- **PostgreSQLSession**: Individual client session handling
|
|
- **PostgreSQLServerConfig**: Server configuration options
|
|
- **Authentication System**: Trust, password, and MD5 authentication
|
|
- **TLS Support**: Encrypted connections with custom certificates
|
|
- **Connection Pooling**: Resource management and cleanup
|
|
|
|
### `protocol.go`
|
|
- **Wire Protocol Implementation**: Full PostgreSQL 3.0 protocol support
|
|
- **Message Handlers**: Startup, query, parse/bind/execute sequences
|
|
- **Response Generation**: Row descriptions, data rows, command completion
|
|
- **Data Type Mapping**: SeaweedFS to PostgreSQL type conversion
|
|
- **SQL Parser**: Uses PostgreSQL-native parser for full dialect compatibility
|
|
- **Error Handling**: PostgreSQL-compliant error responses
|
|
- **MQ Integration**: Direct integration with SeaweedFS SQL engine for real topic data
|
|
- **System Query Support**: Essential PostgreSQL system queries (version, current_user, etc.)
|
|
- **Database Context**: Session-based database switching with USE commands
|
|
|
|
## Key Features
|
|
|
|
### Real MQ Topic Integration
|
|
The PostgreSQL server now directly integrates with SeaweedFS Message Queue topics, providing:
|
|
|
|
- **Live Topic Discovery**: Automatically discovers MQ namespaces and topics from the filer
|
|
- **Real Schema Information**: Reads actual topic schemas from broker configuration
|
|
- **Actual Data Access**: Queries real MQ data stored in Parquet and log files
|
|
- **Dynamic Updates**: Reflects topic additions and schema changes automatically
|
|
- **Consistent SQL Engine**: Uses the same SQL engine as `weed-sql` command
|
|
|
|
### Database Context Management
|
|
- **Session Isolation**: Each PostgreSQL connection has its own database context
|
|
- **USE Command Support**: Switch between namespaces using standard `USE database` syntax
|
|
- **Auto-Discovery**: Topics are discovered and registered on first access
|
|
- **Schema Caching**: Efficient caching of topic schemas and metadata
|
|
|
|
## Usage
|
|
|
|
### Import the Package
|
|
```go
|
|
import "github.com/seaweedfs/seaweedfs/weed/server/postgres"
|
|
```
|
|
|
|
### Create and Start Server
|
|
```go
|
|
config := &postgres.PostgreSQLServerConfig{
|
|
Host: "localhost",
|
|
Port: 5432,
|
|
AuthMethod: postgres.AuthMD5,
|
|
Users: map[string]string{"admin": "secret"},
|
|
Database: "default",
|
|
MaxConns: 100,
|
|
IdleTimeout: time.Hour,
|
|
}
|
|
|
|
server, err := postgres.NewPostgreSQLServer(config, "localhost:9333")
|
|
if err != nil {
|
|
return err
|
|
}
|
|
|
|
err = server.Start()
|
|
if err != nil {
|
|
return err
|
|
}
|
|
|
|
// Server is now accepting PostgreSQL connections
|
|
```
|
|
|
|
## Authentication Methods
|
|
|
|
The package supports three authentication methods:
|
|
|
|
### Trust Authentication
|
|
```go
|
|
AuthMethod: postgres.AuthTrust
|
|
```
|
|
- No password required
|
|
- Suitable for development/testing
|
|
- Not recommended for production
|
|
|
|
### Password Authentication
|
|
```go
|
|
AuthMethod: postgres.AuthPassword,
|
|
Users: map[string]string{"user": "password"}
|
|
```
|
|
- Clear text password transmission
|
|
- Simple but less secure
|
|
- Requires TLS for production use
|
|
|
|
### MD5 Authentication
|
|
```go
|
|
AuthMethod: postgres.AuthMD5,
|
|
Users: map[string]string{"user": "password"}
|
|
```
|
|
- Secure hashed authentication with salt
|
|
- **Recommended for production**
|
|
- Compatible with all PostgreSQL clients
|
|
|
|
## TLS Configuration
|
|
|
|
Enable TLS encryption for secure connections:
|
|
|
|
```go
|
|
cert, err := tls.LoadX509KeyPair("server.crt", "server.key")
|
|
if err != nil {
|
|
return err
|
|
}
|
|
|
|
config.TLSConfig = &tls.Config{
|
|
Certificates: []tls.Certificate{cert},
|
|
}
|
|
```
|
|
|
|
## Client Compatibility
|
|
|
|
This implementation is compatible with:
|
|
|
|
### Command Line Tools
|
|
- `psql` - PostgreSQL command line client
|
|
- `pgcli` - Enhanced command line with auto-completion
|
|
- Database IDEs (DataGrip, DBeaver)
|
|
|
|
### Programming Languages
|
|
- **Python**: psycopg2, asyncpg
|
|
- **Java**: PostgreSQL JDBC driver
|
|
- **JavaScript**: pg (node-postgres)
|
|
- **Go**: lib/pq, pgx
|
|
- **.NET**: Npgsql
|
|
- **PHP**: pdo_pgsql
|
|
- **Ruby**: pg gem
|
|
|
|
### BI Tools
|
|
- Tableau (native PostgreSQL connector)
|
|
- Power BI (PostgreSQL data source)
|
|
- Grafana (PostgreSQL plugin)
|
|
- Apache Superset
|
|
|
|
## Supported SQL Operations
|
|
|
|
### Data Queries
|
|
```sql
|
|
SELECT * FROM topic_name;
|
|
SELECT id, message FROM topic_name WHERE condition;
|
|
SELECT COUNT(*) FROM topic_name;
|
|
SELECT MIN(id), MAX(id), AVG(amount) FROM topic_name;
|
|
```
|
|
|
|
### Schema Information
|
|
```sql
|
|
SHOW DATABASES;
|
|
SHOW TABLES;
|
|
DESCRIBE topic_name;
|
|
DESC topic_name;
|
|
```
|
|
|
|
### System Information
|
|
```sql
|
|
SELECT version();
|
|
SELECT current_database();
|
|
SELECT current_user;
|
|
```
|
|
|
|
### System Columns
|
|
```sql
|
|
SELECT id, message, _timestamp_ns, _key, _source FROM topic_name;
|
|
```
|
|
|
|
## Configuration Options
|
|
|
|
### Server Configuration
|
|
- **Host/Port**: Server binding address and port
|
|
- **Authentication**: Method and user credentials
|
|
- **Database**: Default database/namespace name
|
|
- **Connections**: Maximum concurrent connections
|
|
- **Timeouts**: Idle connection timeout
|
|
- **TLS**: Certificate and encryption settings
|
|
|
|
### Performance Tuning
|
|
- **Connection Limits**: Prevent resource exhaustion
|
|
- **Idle Timeout**: Automatic cleanup of unused connections
|
|
- **Memory Management**: Efficient session handling
|
|
- **Query Streaming**: Large result set support
|
|
|
|
## Error Handling
|
|
|
|
The package provides PostgreSQL-compliant error responses:
|
|
|
|
- **Connection Errors**: Authentication failures, network issues
|
|
- **SQL Errors**: Invalid syntax, missing tables
|
|
- **Resource Errors**: Connection limits, timeouts
|
|
- **Security Errors**: Permission denied, invalid credentials
|
|
|
|
## Development and Testing
|
|
|
|
### Unit Tests
|
|
Run PostgreSQL package tests:
|
|
```bash
|
|
go test ./weed/server/postgres
|
|
```
|
|
|
|
### Integration Testing
|
|
Use the provided Python test client:
|
|
```bash
|
|
python postgres-examples/test_client.py --host localhost --port 5432
|
|
```
|
|
|
|
### Manual Testing
|
|
Connect with psql:
|
|
```bash
|
|
psql -h localhost -p 5432 -U seaweedfs -d default
|
|
```
|
|
|
|
## Documentation
|
|
|
|
- **DESIGN.md**: Complete architecture and design overview
|
|
- **IMPLEMENTATION.md**: Detailed implementation guide
|
|
- **postgres-examples/**: Client examples and test scripts
|
|
- **Command Documentation**: `weed-db -help`
|
|
|
|
## Security Considerations
|
|
|
|
### Production Deployment
|
|
- Use MD5 or stronger authentication
|
|
- Enable TLS encryption
|
|
- Configure appropriate connection limits
|
|
- Monitor for suspicious activity
|
|
- Use strong passwords
|
|
- Implement proper firewall rules
|
|
|
|
### Access Control
|
|
- Create dedicated read-only users
|
|
- Use principle of least privilege
|
|
- Monitor connection patterns
|
|
- Log authentication attempts
|
|
|
|
## Architecture Notes
|
|
|
|
### SQL Parser Dialect Considerations
|
|
|
|
**✅ POSTGRESQL ONLY**: SeaweedFS SQL engine exclusively supports PostgreSQL syntax:
|
|
|
|
- **✅ Core Engine**: `engine.go` uses custom PostgreSQL parser for proper dialect support
|
|
- **PostgreSQL Server**: Uses PostgreSQL parser for optimal wire protocol compatibility
|
|
- **Parser**: Custom lightweight PostgreSQL parser for full PostgreSQL compatibility
|
|
- **Support Status**: Only PostgreSQL syntax is supported - MySQL parsing has been removed
|
|
|
|
**Key Benefits of PostgreSQL Parser**:
|
|
- **Native Dialect Support**: Correctly handles PostgreSQL-specific syntax and semantics
|
|
- **System Catalog Compatibility**: Supports `pg_catalog`, `information_schema` queries
|
|
- **Operator Compatibility**: Handles `||` string concatenation, PostgreSQL-specific operators
|
|
- **Type System Alignment**: Better PostgreSQL type inference and coercion
|
|
- **Reduced Translation Overhead**: Eliminates need for dialect translation layer
|
|
|
|
**PostgreSQL Syntax Support**:
|
|
- **Identifier Quoting**: Uses PostgreSQL double quotes (`"`) for identifiers
|
|
- **String Concatenation**: Supports PostgreSQL `||` operator
|
|
- **System Functions**: Full support for PostgreSQL system catalogs (`pg_catalog`) and functions
|
|
- **Standard Compliance**: Follows PostgreSQL SQL standard and dialect
|
|
|
|
**Implementation Features**:
|
|
- Native PostgreSQL query processing in `protocol.go`
|
|
- System query support (`SELECT version()`, `BEGIN`, etc.)
|
|
- Type mapping between PostgreSQL and SeaweedFS schema types
|
|
- Error code mapping to PostgreSQL standards
|
|
- Comprehensive PostgreSQL wire protocol support
|
|
|
|
This package provides enterprise-grade PostgreSQL compatibility, enabling seamless integration of SeaweedFS with the entire PostgreSQL ecosystem.
|