pg_squeeze | A PostgreSQL extension for automatic bloat cleanup

by cybertec-postgresql C Version: REL1_5_0 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | pg_squeeze Summary

pg_squeeze is a C library. pg_squeeze has no bugs, it has no vulnerabilities and it has low support. However pg_squeeze has a Non-SPDX License. You can download it from GitHub.

pg_squeeze is an extension that removes unused space from a table and optionally sorts tuples according to particular index (as if CLUSTER [2] command was executed concurrently with regular reads / writes). In fact we try to replace pg_repack [1] extension. While providing very similar functionality, pg_squeeze takes a different approach as it. While 1) makes both configuration and use simpler (compared to [1] which uses both server and client side code), it also allows for rather smooth implementation of unattended processing using background workers [3]. As for 2), one important difference (besides the use of background workers) is that we use logical decoding [4] instead of triggers to capture concurrent changes.

Support

Quality

Security

License

Reuse

Support

pg_squeeze has a low active ecosystem.

It has 323 star(s) with 22 fork(s). There are 15 watchers for this library.

It had no major release in the last 6 months.

There are 24 open issues and 27 have been closed. On average issues are closed in 100 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of pg_squeeze is REL1_5_0

Quality

pg_squeeze has 0 bugs and 0 code smells.

Security

pg_squeeze has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

pg_squeeze code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

pg_squeeze has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

pg_squeeze releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of pg_squeeze

Get all kandi verified functions for this library.

pg_squeeze Key Features

No Key Features are available at this moment for pg_squeeze.

pg_squeeze Examples and Code Snippets

No Code Snippets are available at this moment for pg_squeeze.

Community Discussions

Trending Discussions on pg_squeeze

What is difference between pg_squeeze and pg_repack?

QUESTION

What is difference between pg_squeeze and pg_repack?

Asked 2022-Feb-21 at 14:36

I've been working on optimizing tables in database. One of our table requires monthly vacuuming because of cleaning up processes.pg_squeeze Table size can get upto 25 GB. As this table is used by production users, we can't afford downtime every month to run VACUUM FULL.

I found that pg_squeeze and pg_repack can be used for this purpose. But I'm not able to understand the difference between those two. Can someone please explain what is the difference and which will be more suitable for me to use?

Thank you.

...

ANSWER

Answered 2022-Feb-11 at 09:22

The main difference is that pg_queeze operates entirely inside the database, with no need for an external binary. It also has a background worker that will schedule table rewrites automatically if certain criteria are met.

So you could say that pg_repack is less invasive (for example, installation requires no restart of the database), but pg_squeeze is more feature complete.

Disclaimer: I work for the company who wrote pg_squeeze.

Source https://stackoverflow.com/questions/71077403

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install pg_squeeze

Set PG_CONFIG environment variable to point to pg_config command of your PostgreSQL installation.
Set PG_CONFIG environment variable to point to pg_config command of your PostgreSQL installation.
make
sudo make install
Apply the following settings to postgresql.conf: wal_level = logical max_replication_slots = 1 # ... or add 1 to the current value. shared_preload_libraries = 'pg_squeeze' # ... or add the library to the existing ones.
Start the PG cluster.
As a superuser, run CREATE EXTENSION pg_squeeze;
CAUTION! As there's no straightforward way to migrate the scheduling information (see the notes on the "schedule" column of the "squeeze"."tables" table) automatically, and as the "schedule" column must not contain NULL values, the upgrade deletes the contents of the "squeeze"."tables" table. Please export the table contents to a file before you perform the upgrade and configure the checks of those tables again as soon as the upgrade is done.
Set PG_CONFIG environment variable to point to pg_config command of your PostgreSQL installation.
make
Stop the PG instance
sudo make install
Restart the PG instance
Connect to each database containing pg_squeeze 1.2.x and run this command: ALTER EXTENSION pg_squeeze UPDATE;

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: