Wed Mar 7 16:28:40 PST 2012
- Previous message: [Slony1-general] A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
- Next message: [Slony1-general] A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Mar 7, 2012 at 2:37 PM, Steve Singer <ssinger at ca.afilias.info> wrote: > On 12-03-07 03:59 PM, Aleksey Tsalolikhin wrote: >> >> Hello, > > > > If the problem is that your table is bloated > > The CLUSTER command > http://www.postgresql.org/docs/8.4/static/sql-cluster.html will compact your > table. The VACUUM command does not normally return unused space to the > operating system (some exceptions apply) Thank you, Steve. I used "check_postgres" to check for bloat and it reported wasted size only 1 GB. table XYZ rows:8674174 pages:463848 shouldbe:318436 (1.5X) wasted size:1191215104 (1 GB) This does not seem much compared to table size on the master, 154 GB,and on the slave, 527 GB. I can't run CLUSTER because I don't have another 500 GB free... I am running VACUUM FULL right now to return the unused disk space to the OS. I wondering if it will free 1 GB or 300 GB. I expect 1 GB, based on the check_postgres "bloat" check results. I'll run check_postgres "bloat" check again after the VACUUM FULL finishes. This table does use TOAST and most of the data is in TOAST... I wonder if the 1 GB size includes TOAST. Best, Aleksey
- Previous message: [Slony1-general] A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
- Next message: [Slony1-general] A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list