Re: Dead rows not getting removed during vacuum

From: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
To: Granthana Biswas <granthana(at)zedo(dot)com>
Cc: PostgreSQL General Discussion Forum <pgsql-general(at)postgresql(dot)org>
Subject: Re: Dead rows not getting removed during vacuum
Date: 2014-03-21 15:21:12
Message-ID: CAL_0b1tPrAQiyVxcXhKukhZxH9-sffwAcnXCm8ECbtHrepOhCA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Mar 21, 2014 at 2:46 AM, Granthana Biswas <granthana(at)zedo(dot)com> wrote:
> We don't have two-phase commit prepared transactions. During vacuum, along with this problem we are also facing streaming replication issue. Hundreds of xlogs are in ready state in pg_xlog/archive_status. Those are being copied manually after vacuum otherwise rsync happens very slowly and replication lag keeps increasing.

Okay, I see. Then next questions are:

What postgres version is it?
What max_standby_archive_delay and max_standby_streaming_delay are set to?
Are there any long running activity or idling in transaction backends
on your slaves?

--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA

http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Glenn Pierce 2014-03-21 15:55:02 Passing array of range literals
Previous Message Ashmita Jain 2014-03-21 10:16:57 COPY error with null date