Dear Simon,
On Fri, May 08, 2009 at 07:15:19PM +0100, Simon Riggs wrote:
! > Server becomes very slow while tremendous amounts of data are written
! > to WAL logs - disk activity log shows 600 MB of effective write
! > requests before each 16 MB WAL log is archived and recycled.
!
! VACUUM FULL
On Fri, 2009-05-08 at 12:26 +, Peter Much wrote:
> Server becomes very slow while tremendous amounts of data are written
> to WAL logs - disk activity log shows 600 MB of effective write
> requests before each 16 MB WAL log is archived and recycled.
VACUUM FULL does many things, most of them
Dear Rafael,
I agree with You. And that is actually what I have done up to now,
although for a different reason: the amount of WAL logs produced
by VACUUM FULL is practically unpredictable and can be much more than
the database size, and since that database belongs to the backup system,
the backup
Peter Much wrote:
>
> I perceived it only during "vaccum full" yet, but then a long-running
> "vacuum full" on a large table is the only significant activity on the
> server. (I know that "vacuum full" may not be really necessary, but
> I think it should practically function.)
>
[..]
Hei
The following bug has been logged online:
Bug reference: 4801
Logged by: Peter Much
Email address: p...@citylink.dinoex.sub.org
PostgreSQL version: 8.2.13
Operating system: FreeBSD 7.2
Description:Performance failure: 600 MB written to each WAL log
Details:
Server b
