pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: SBob <sbob@quadratum-braccas.com>
To: Rui DeSousa <rui@crazybean.net>
To: Keith <keith@keithf4.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Vacuum not cleaning up rows.
Date: Fri, 21 Jun 2019 09:51:09 -0400
Message-ID: <ef2d3985-cbb4-4d42-a06a-0c8163dc85a7@www.fastmail.com> (raw)
In-Reply-To: <02C3BE5C-ED36-4B36-85C3-90C774FA528B@crazybean.net>
References: <15eddc60-6441-e55e-f742-bd7ea37f1873@quadratum-braccas.com>
	<31037.1560988222@sss.pgh.pa.us>
	<053c95f2-1425-23ac-0308-ca22887db156@quadratum-braccas.com>
	<CAHw75vuMizA6F0B+DTbbyG09GYfc8X2d5E+QKt75uXot4bquiA@mail.gmail.com>
	<02C3BE5C-ED36-4B36-85C3-90C774FA528B@crazybean.net>

I do see older backend_start values (from around 6 hours ago). However I am confused as to how a connection to one database in a cluster can prevenr vacuum from cleaning up row versions in a table within another database. How is that possible since onle one database has access to this table?



On Thu, Jun 20, 2019, at 2:37 PM, Rui DeSousa wrote:
> 
> In addition to what others have already stated to check; also check for replication slots.
> 
> 
> select * from pg_replication_slots;
> 
> 

view thread (8+ messages)  latest in thread

Message-ID: <ef2d3985-cbb4-4d42-a06a-0c8163dc85a7@www.fastmail.com>
Permalink:  ../ef2d3985-cbb4-4d42-a06a-0c8163dc85a7@www.fastmail.com/
Also on:    postgresql.org/message-id/ef2d3985-cbb4-4d42-a06a-0c8163dc85a7@www.fastmail.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: sbob@quadratum-braccas.com, rui@crazybean.net, keith@keithf4.com, tgl@sss.pgh.pa.us
  Subject: Re: Vacuum not cleaning up rows.
  In-Reply-To: <ef2d3985-cbb4-4d42-a06a-0c8163dc85a7@www.fastmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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