| From: | Granthana Biswas <granthana(at)zedo(dot)com> |
|---|---|
| To: | Venkata Balaji Nagothi <vbnpgc(at)gmail(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 05:20:37 |
| Message-ID: | CAACh-pXFm4Ymw1cXGpQ8Av39RT7zYHn5FdsKD049pRnEfWJ9Aw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Venkata,
No there are no other connections to the DB during vacuum.
Regards,
Granthana
On Fri, Mar 21, 2014 at 3:12 AM, Venkata Balaji Nagothi <vbnpgc(at)gmail(dot)com>wrote:
> On Thu, Mar 20, 2014 at 5:27 AM, Granthana Biswas <granthana(at)zedo(dot)com>wrote:
>
> Hello All,
>>
>> Has anyone ever faced the issue of dead rows not getting removed during
>> vacuum even if there are no open transactions/connections?
>>
>> We have been facing this during every scheduled vacuum which is done
>> after closing all other database connections:
>>
>> 119278 dead row versions cannot be removed yet.
>>
>> This means there are transactions in progress when the vacuum was
> running. Do you see any such situation ?
>
> Please let us know, which version of PostgreSQL is this.
>
> Venkata Balaji N
>
> Sr. Database Administrator
> Fujitsu Australia
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Granthana Biswas | 2014-03-21 09:46:36 | Re: Dead rows not getting removed during vacuum |
| Previous Message | Venkata Balaji Nagothi | 2014-03-21 01:21:24 | Re: Hot standby read slaves exceed max delay on WAL segment. Replication lag. |