well yes, as the system is "live", users are browsing the website. but
all queries that try to access the table in question are stalled at the
moment. when querying server status i'm seeing lots of queries that are
waiting for access to the table.
would vacuum freeze be faster?
Vacuum freeze
Thomas H. wrote:
this somehow sounds buggy:
vacuum full absolutely *will* bloat your index, if run on a
heavily-modified table. I do not think it will bloat pg_xlog by itself
however; are you sure you don't have some other open transactions?
well yes, as the system is "live", users are brows
this somehow sounds buggy:
vacuum full absolutely *will* bloat your index, if run on a
heavily-modified table. I do not think it will bloat pg_xlog by itself
however; are you sure you don't have some other open transactions?
well yes, as the system is "live", users are browsing the website. b
"Thomas H." <[EMAIL PROTECTED]> writes:
> this somehow sounds buggy:
vacuum full absolutely *will* bloat your index, if run on a
heavily-modified table. I do not think it will bloat pg_xlog by itself
however; are you sure you don't have some other open transactions?
> a) .. prevent total diskspa
this somehow sounds buggy:
there's this table forum.posts which had 224mb table size, 145mb toast table
size and 176mb indexes size (aproximately 60'000 rows). as i was doing some
updates of all the records, i've issued a VACUUM FULL ...
this was merely 60min ago, and it hasn't yet finished...
