Re: How to avoid generation huge pg_xlog files during VACUUM , REINDEX maintenance task.

Shrinivas Devarkonda wrote:
> We have a High transactional Database with Streamline Replication in place across two Data Centers
> with the dedicated leased line. The SR works awesome all time.
>
> We do vacuum+reindex of few imp high transactional tables (not an entire database) which generates
> many pg_xlog files indeed creates Huge spike of Data transfer between two networks and burst the
> bandwidth only during this time.
>
> Can we avoid the generating pg_xlog files for vacuum + reindex ? Are any other solutions to it ? Our
> vacuum + reindex is very very minimal and based on dead rows stats.
>
> PG version : 9.0.4 ( on 64 bit OS).

I don't think that your VACUUM and REINDEX is very minimal, because otherwise
it would not generate a lot of WAL (pg_xlog files). The WAL captures the
changes to the database, and they must be replayed to the standby.

If you really need these maintenance operations, that's the price.

Yours,
Laurenz Albe