pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
(auto) vacuum mysterious
2+ messages / 2 participants
[nested] [flat]

* (auto) vacuum mysterious
@ 2017-02-14 10:15 walpino@gmail.com
  2017-02-14 14:52 ` Re: (auto) vacuum mysterious Alvaro Herrera <alvherre@2ndquadrant.com>
  0 siblings, 1 reply; 2+ messages in thread

From: walpino@gmail.com @ 2017-02-14 10:15 UTC (permalink / raw)
  To: pgsql-admin

Hi There 

My Name is Martin
And we are running PostgreSQL 9.5.3 

We are doing a lot of deletes updates and Inserts on some tables

Until now we didn’t Encounter so much Problems with the vacuumizer but in the last view days we have the fact the vacuum cannot remove dead rows anymore

I know it is the case when there are other Long running Transactions running but this isn’t the case


The vacuum Output Shows only that it cannot remove dead rows.
But not why?

Is there a way to see futher Information to see that? To see which session is blocking the vacuum Job?

Thanks Martin




DETAIL:  2066873 dead row versions cannot be removed yet.
There were 685985 unused item pointers.
Skipped 0 pages due to buffer pins.
0 pages are entirely empty.
CPU 1.75s/1.07u sec elapsed 2.84 sec.
INFO:  vacuuming "pg_toast.pg_toast_30145032"
INFO:  index "pg_toast_30145032_index" now contains 0 row versions in 1 pages
DETAIL:  0 index row versions were removed.
0 index pages have been deleted, 0 are currently reusable.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  "pg_toast_30145032": found 0 removable, 0 nonremovable row versions in 0 out of 0 pages
DETAIL:  0 dead row versions cannot be removed yet.
There were 0 unused item pointers.
Skipped 0 pages due to buffer pins.
0 pages are entirely empty.
CPU 0.00s/0.00u sec elapsed 0.00 sec.
VACUUM

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: (auto) vacuum mysterious
  2017-02-14 10:15 (auto) vacuum mysterious walpino@gmail.com
@ 2017-02-14 14:52 ` Alvaro Herrera <alvherre@2ndquadrant.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Alvaro Herrera @ 2017-02-14 14:52 UTC (permalink / raw)
  To: walpino@gmail.com; +Cc: pgsql-admin

walpino@gmail.com wrote:
> Hi There 
> 
> My Name is Martin
> And we are running PostgreSQL 9.5.3 
> 
> We are doing a lot of deletes updates and Inserts on some tables
> 
> Until now we didn’t Encounter so much Problems with the vacuumizer but in the last view days we have the fact the vacuum cannot remove dead rows anymore
> 
> I know it is the case when there are other Long running Transactions running but this isn’t the case

Maybe you have an inactive replication slot.  See
  select * from pg_replication_slots;
and consider dropping those that are unused.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2017-02-14 14:52 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-02-14 10:15 (auto) vacuum mysterious walpino@gmail.com
2017-02-14 14:52 ` Alvaro Herrera <alvherre@2ndquadrant.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox