pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: haster (@haster) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #3728: fix: ensure extended protocol messages end with Sync message
Date: Mon, 11 Aug 2025 11:44:52 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
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.
view thread (15+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] PR #3728: fix: ensure extended protocol messages end with Sync message
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox