> Date: Mon, 22 Sep 2014 12:46:21 -0700
> From: pierce(at)hogranch(dot)com
> To: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] large table
>
> On 9/22/2014 12:33 PM, Luke Coldiron wrote:
> >
> > It is possible and that is part of what I am trying to discover
> > however I am very familiar with the system / code base and in this
> > case there is a single process updating the timestamp and a single
> > process reading the timestamp. There are no other user processes
> > programmed to interact with this table outside of potentially what
> > Postgres is doing.
>
> ANY other connection to the same postgres server, even to a different
> database, that has an open long running transaction (most frequently,
> "Idle In Transaction") will block autovacuum from marking the old tuples
> as reusable.
>
Good point, I wasn't thinking about this as a possibility. This is a very good possibility considering the behavior of the rest of the system.
>
> --
> john r pierce 37N 122W
> somewhere on the middle of the left coast
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general