Message-ID: <gh-pgjdbc-pgjdbc-3728-c3174423755@github.com>
From: "haster (@haster)" <noreply+haster@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 11 Aug 2025 11:44:52 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3728: fix: ensure extended protocol messages end with Sync message
In-Reply-To: <gh-pgjdbc-pgjdbc-3728@github.com>
References: <gh-pgjdbc-pgjdbc-3728@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: haster
X-GitHub-Comment-Id: 3174423755
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2025-08-11T11:45:18Z
X-GitHub-Issue: 3728
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3728#issuecomment-3174423755
Content-Type: text/plain; charset=utf-8

As to your question about pgpool in the docker compose, we build our own postgres and pgpool so I'm not sure how our experience translates to your situation.

Our docker-compose.yml looks something like the following:

```yaml
services:
  db:
    container_name: "db"
    image: ...
    env_file: db.env
    
    networks:
      network:
        ipv4_address: << db_ip >>
    read_only: True
    tmpfs:
      - /run:rw,noexec,nosuid,size=64k
    volumes:
      - /data/db:/var/lib/postgresql/data
      - /var/log/db:/var/log/postgresql


  tkh-pgpool:
    container_name: "pgpool"
    image: ...
    depends_on:
      - db
    env_file: db.env

    networks:
      network:
        ipv4_address: << pgpool_ip  >>
    read_only: True
    tmpfs:
      - /run/postgresql:rw,noexec,nosuid,size=64k,uid=208,gid=208
      - /tmp:rw,noexec,nosuid,size=64k
    volumes:
      - /data/pgpool:/etc/pgpool2:ro
```

The db.env file holds nothing special, postgres user credentials and such.