On 1/13/20 7:41 AM, dagamier wrote:
Can't afford the downtime of a "vaccuum full" and the autovacuum process is
not cleaning up all the dead space tied up by the database. pg_repack works
great on my test database in reclaiming disk space (in my tests I got back
46% of my disk space back) due to
Can't afford the downtime of a "vaccuum full" and the autovacuum process is
not cleaning up all the dead space tied up by the database. pg_repack works
great on my test database in reclaiming disk space (in my tests I got back
46% of my disk space back) due to all the deletions that happen in our
t
On 1/10/20 10:01 AM, dagamier wrote:
I have two databases that are clustered. One is my primary (DB1) and the
other is my secondary (DB2). Both have the same tables and schemas. Could I
use pg_repack against each of these separately (I am wanting to do this at a
"by table" level) to clean up dead
I have two databases that are clustered. One is my primary (DB1) and the
other is my secondary (DB2). Both have the same tables and schemas. Could I
use pg_repack against each of these separately (I am wanting to do this at a
"by table" level) to clean up dead space that hasn't been returned? Shoul
