Tue, 07 May 2024 16:16:08 +0000 en-US hourly 1 https://wordpress.org/?v=6.5.2 https://www.percona.com/blog/wp-content/uploads/2023/02/cropped-percona-favicon-32x32.png 32 32 76301791 https://www.percona.com/blog/speed-up-repetitive-postgresql-statements-with-gexec/ https://www.percona.com/blog/speed-up-repetitive-postgresql-statements-with-gexec/#respond Tue, 07 May 2024 16:15:05 +0000 https://www.percona.com/blog/?p=96166 Last week, we were assisting a client who needed to resolve an issue related to partitioned tables.Often, a table can include dozens or even hundreds of partitions. Unfortunately, some object-level parameters for tuning (like storage_parameter) cannot be modified from the parent table and must be manipulated directly through the child table. As a result, we […]]]> https://www.percona.com/blog/speed-up-repetitive-postgresql-statements-with-gexec/feed/ 0 96166 https://www.percona.com/blog/five-reasons-why-wal-segments-accumulate-in-the-pg_wal-directory-in-postgresql/ https://www.percona.com/blog/five-reasons-why-wal-segments-accumulate-in-the-pg_wal-directory-in-postgresql/#respond Tue, 02 Apr 2024 13:48:56 +0000 https://www.percona.com/blog/?p=95470 One of the most frequent concerns we see in the Percona support team is: Why is my pg_wal growing? / pg_wal is filling up the filesystem / pg_wal does not release the space, and so on.In PostgreSQL, the pg_wal directory plays a crucial role in managing the Write-Ahead Logging (WAL) mechanism, which ensures the durability […]]]> https://www.percona.com/blog/five-reasons-why-wal-segments-accumulate-in-the-pg_wal-directory-in-postgresql/feed/ 0 95470