Skip to content

Conversation

smoya
Copy link
Contributor

@smoya smoya commented May 7, 2025

We didn't update the compose-dev.yaml file since the repackaging. That means we were not installing pgai in the DB and we were still asking the user to install the extension.

Additionally, we were using the wrong postgres PGDATA path. In particular, we were setting /home/postgres/pgdata/data instead of the default in postgres /var/lib/postgresql/data because is the one we use in timescaledb-docker-ha.
That means data was never persisted in the host volume.

@smoya smoya requested a review from a team as a code owner May 7, 2025 12:02
@smoya smoya temporarily deployed to internal-contributors May 7, 2025 12:02 — with GitHub Actions Inactive
for i in $(seq 1 10); do
echo "Attempt $$i: installing pgai..."
# always overwriting previous installation here.
python -m pgai install -d postgres://postgres:postgres@db:5432/postgres && exit 0
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not using --strict here as this is a dev env.

Copy link
Contributor

@Askir Askir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@smoya smoya temporarily deployed to internal-contributors May 8, 2025 09:23 — with GitHub Actions Inactive
@smoya smoya force-pushed the sergio-docker-compose branch from 4a80edb to a7acfbc Compare May 9, 2025 08:36
@smoya smoya temporarily deployed to internal-contributors May 9, 2025 08:36 — with GitHub Actions Inactive
@smoya smoya merged commit b87c5a3 into main May 9, 2025
15 checks passed
@smoya smoya deleted the sergio-docker-compose branch May 9, 2025 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants