I ran the following query on my database:
update bv_descriptions set description = REPLACE(description, '\\n', '\n');
It finished fine but to my surprise when I ran "df" on the server the
drive usage jumped from 44% to 60% which is additional 650MB.
I tried to restart the server but it didn't do any good, eventually I
tried to do a FULL VACUUM on that table and it did the trick and
cleaned the lost space.
I am still confused about what happened... What took these additional 650MB?
I could understand this phenomenon if it happened before I did
COMMIT... But why did it stay after COMMIT too?
pgsql-novice by date
|Next:||From: Tom Lane||Date: 2004-07-03 15:24:32|
|Subject: Re: createlang doesn't work |
|Previous:||From: R.Welz||Date: 2004-07-03 12:51:29|
|Subject: createlang doesn't work|