pg_squeeze icon indicating copy to clipboard operation
pg_squeeze copied to clipboard

A PostgreSQL extension for automatic bloat cleanup

Results 9 pg_squeeze issues
Sort by recently updated
recently updated
newest added

I installed `pg_squeeze` from the master branch, it caused the database to go into recovery mode when I ran `squeeze.squeeze_table`. I tried reinstalling it with `REL1_6` by following these steps:...

Hi I'm using squeeze `REL1_6`, and I have an issue on some server All servers running postgresql v14.11 All servers have the same pg_squeeze version pg_squeeze configuration in `postgresql.conf` is...

bug

Hi, This query is regarding the README information that says `make sure that your table has either primary key or unique constraint`. ``` postgres=# create table test ( id int,...

question

Hello, I have observed that running pg_squeeze on large tables either manually or on a schedule, leads to replication lag building constantly and requires intervention to prevent continuous WAL growth....

question

I'm trying to squeeze a large table with a lot of bloat. The worker seems to make it almost all the way through the squeeze process -- from `squeeze.get_active_workers()` I...

Looks like the document adjustment for the below issue isn't done. https://github.com/cybertec-postgresql/pg_squeeze/issues/69

The function signature for ReplicationSlotAcquire changed and now requires a third parameter. There is also now a macro to get the tuple descriptor attribute.

Most of the time, pg_squeeze is unsuccessful in my databases and returns the error: 'initial slot snapshot too large.' Is there any way to resolve this issue? Currently, wal_keep_size is...

The below check in **pg_squeeze.c** needs adjustment since we no longer support Postgres 12. ``` #if PG_VERSION_NUM < 120000 #error "PostgreSQL version 12 or higher is required" #endif ```