| From: | Haribabu Kommi <kommi(dot)haribabu(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-20 23:40:38 |
| Message-ID: | CAJrrPGfXyFi7bQMC7tzW=akhnH3dgme-8xRFF9QG0iSbz8Dmyw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Mar 20, 2014 at 11:27 PM, 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.
These are the dead tuples which occurred after the vacuum operation is
started. These tuples may be visible to the other transactions,
because of this reason It cannot remove these tuples in this vacuum
scan. In the next vacuum these will be cleaned. You can observe the
same in the next vacuum.
Regards,
Hari Babu
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Venkata Balaji Nagothi | 2014-03-21 01:21:24 | Re: Hot standby read slaves exceed max delay on WAL segment. Replication lag. |
| Previous Message | Sergey Konoplev | 2014-03-20 22:06:16 | Re: Dead rows not getting removed during vacuum |