Search Postgresql Archives

Re: TOAST Table / Dead Tuples / Free Pages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Hi Shenavai,

Here are some more options..

VACUUM <your tablename>

VACUUM  FULL <your tablename>

You may also reindex to reclaim space

REINDEX TABLE <your tablename>

REINDEX INDEX <indexname>


Regards,
Muhammad Ikram
Bitnine 

On Thu, Jun 13, 2024 at 1:09 PM Kashif Zeeshan <kashi.zeeshan@xxxxxxxxx> wrote:
Hi

You can use the CLUSTER command, which will physically reorder the table based on index, effectively reducing the size of the table without using VACUUM.

CLUSTER your_table USING your_index;

Or you can use the pg_repack extension as well.

pg_repack -d your_database -t your_table

Regards
Kashif Zeeshan



On Thu, Jun 13, 2024 at 12:55 PM Shenavai, Manuel <manuel.shenavai@xxxxxxx> wrote:

Hi everyone,

 

I created a simple scenario to understand the handling of TOASTs: There is an empty database with a single table and record. The single record gets updated multiple times with 10MB (bytea column). I can see that the table/toasttable size is growing (500MB).

 

Now I tried to find a way to get the DB size down again (it should be around 10MB instead of 500MB). I don’t want to use VACUUM FULL due to the exclusive lock.

 

Is there any way to remove the dead tuples and free the pages?

 

Thanks in advance &

Best regards,

Manuel

 



--
Muhammad Ikram


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux