A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/CHERTS/pg_repack_docker below:

CHERTS/pg_repack_docker: Docker image with 'pg_repack' (PostgreSQL extension) installed, can be used 'client-side' to run/invoke pg_repack functionality for a PostgreSQL database with the extension installed.

pg_repack docker image (using alpine linux)

Docker image with 'pg_repack' (PostgreSQL extension) installed, can be used 'client-side' to run/invoke pg_repack functionality for a PostgreSQL database with the extension installed.

Reference: https://github.com/reorg/pg_repack

This images follows the pg_repack releases + compatibility with PostgreSQL.

image postgres pg_repack cherts/pg-repack:1.5.2 17 1.5.2 cherts/pg-repack:1.5.1 17 1.5.1 cherts/pg-repack:1.5.0 16 1.5.0 cherts/pg-repack:1.4.8 15 1.4.8 cherts/pg-repack:1.4.7 14 1.4.7 cherts/pg-repack:1.4.6 13 1.4.6 cherts/pg-repack:1.4.5 12 1.4.5

https://hub.docker.com/r/cherts/pg-repack/

git clone https://github.com/CHERTS/pg_repack_docker.git
cd pg_repack_docker
./build.sh

This image contains the pg_repack utility to run with the official images postgres docker image

This image may be required to run pg_repack on your computer if your postgres is running in cloud or in a container (kubernetes) that already has the pg_repack extension.

# use pg_repack v1.5.0
docker run -it --rm --name pg_repack cherts/pg-repack:1.5.0 --version
# use dry-run mode
docker run -it --rm --name pg_repack \
-e PGPASSWORD=<password> -e "PGOPTIONS='-c idle_in_transaction_session_timeout=0'" \
cherts/pg-repack:1.5.0 --host=X.X.X.X --username=postgres --dbname=dbname --table=table1 \
--no-superuser-check --echo --jobs=2 --dry-run
Additional utilities in this image

This image contains the ability to run additional utilities that come with postgres: psql, pgbench, pg_dump, pg_dumpall, pg_basebackup, pg_restore, pg_verifybackup, pg_controldata and pg_amcheck (pg_createsubscriber and pg_combinebackup only PostgreSQL v17)

For example, we can run pgbench in our cloud database like this:

# use postgres v16
# run init
docker run -it --rm --name pg_repack cherts/pg-repack:1.5.0 pgbench -h X.X.X.X -p 5432 -U postgres test -i -s 10
# run test
docker run -it --rm --name pg_repack cherts/pg-repack:1.5.0 pgbench -h X.X.X.X -p 5432 -U postgres test -T 60 -j 4 -P 2
# run drop test data
docker run -it --rm --name pg_repack cherts/pg-repack:1.5.0 pgbench -h X.X.X.X -p 5432 -U postgres test -i -I d

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4