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

From: Shrinivas Devarkonda <shrinivasdevarkonda(at)gmail(dot)com>
To: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: How to avoid generation huge pg_xlog files during VACUUM , REINDEX maintenance task.
Date: 2014-04-28 13:03:51
Message-ID: CAJavUp1-aStB6yVg_BMWaS+4j=2TPqOppKM0CLCQnA9F24hCAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi All,

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).

Thanks,
Shrinivas Devarkonda.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ray Stell 2014-04-28 14:18:28 9.0.15 WAL mis-replay status?
Previous Message Sergio Mior D&T 2014-04-28 03:18:58 D&T Italia : Time Travel : new development : first release